Ensuring that customers have seamless experiences with setup, support, and use of qualified products & services.

Lync Voice and Video InteroperabilityFrancois DoremieuxLync PG, Skype DivisionMicrosoft Corporation

OUC-B331

Goals

Understand Microsoft’s interoperability investments

Hear the latest on practical voice interop

Discover how Lync 2013 changes video interop

IntroductionLync: interoperability by designLync - Skype federation

Voice interoperabilityPrinciples and technical strategy Technical toolkit: Direct SIP, SBC, Trunking, Media bypass…

Video interoperabilityTowards ubiquitous interop without transcoding

Agenda

IntroductionLync: interoperability by designLync - Skype federation

Voice interoperabilityPrinciples and technical strategy Technical toolkit: Direct SIP, SBC, Trunking, Media bypass…

Video interoperabilityTowards ubiquitous interop without transcoding

Agenda

Interop and coexistence critical for deploymentsLong tailed migration and coexistence, no rip and replace - work with what enterprises have today

Interoperability by design in LyncWell defined, documented scenarios that persist across releases to protect customer investmentsFrom Planning through Spec, Dev, Test, Doc and Sustained Engineering

Three key externally facing channelsIndustry Alliances and Workgroups – UCI Forum, OVCC, ATIS, IETF, ETSI, and 802.11Protocol documentation (all client-server protocols) – Office Protocol DocsScale programs – UC Open Interoperability Program technet.microsoft.com/UCOIP

Principles of Interoperability in Lync

Audio Phones, Endpoints, Handsets, Wireless clients

Video Video Teleconferencing (VTCs), Multipoint Control Units (MCUs), Gateways

Infrastructure Network, PBX, Gateways, Branch Survivability, Session Border Controllers

Services SIP Trunking, E911 Routing

Online Products qualified with Lync Online D

UC Open Interoperability Program

Ensuring that customers have seamless experiences with setup, support, and use of qualified products & services

UC Open Interop: Audio & Video Devices

Aastra 6725 iPAastra 6721 iP Polycom CX600

Polycom CX500

snom 300 UC Edition

$850+$200-300

$150-200$100+

HP 4110

HP 4120

snom 821 UC Edition

Polycom CX3000

IP Phones

USB Audio & Video

Devices

snom 370 UC Edition

Polycom KIRK DECT Wireless

NetworkingWired and Wi-Fi

IP-PBXsTested: Legacy IP-PBXs largely non standards compliant; generally internal testing with caveatsQualified: IP-PBX vendor chooses to test their latest product and passes requirements

GatewaysCircuits on one side, packets with SIP on the other side

Session Border Controller

Packet on one side, different packet on the other

Survivable Branch Appliances Gateways with Lync software for survivability in case of WAN outage

Open Interop Program: Infrastructure

New: Federation between Lync and Skype

https://blogs.technet.com/b/lync/archive/2013/05/23/lync-skype-connectivity-available-today.aspx

IntroductionLync: interoperability by designLync - Skype federation

Voice interoperabilityPrinciples and technical strategyTechnical toolkit: Direct SIP, SBC, Trunking, Media bypass…

Video interoperabilityTowards ubiquitous interop without transcoding

Agenda

Voice interoperability and coexistence scenarios

Enterprise Voice deployments can have different goalsAt least during coexistence and migration phase

Primary business goal, processes, drive approach:Infrastructure refresh (traditional cycles, budgeting…) PBX replacementRapid end user enablement with new technology and experience OverlayInitial evaluation at low risk, coexistence by design (risk averse) Overlay

Significant implications for interop and coexistencePBX replace: most similar to traditional PBX interop approachesOverlay:

While replacing the phone of the user / migrating their line (can be a great alternative)Without removing the user’s phone (hard, confusing and not recommended)

Clarifying the mission statement

Avoid “simring”, “forking and dual forking”Broken scenarios, not designed for, not tested and not supportedWhat happens when Assistant on PBX phone attempts attended transfer to Boss who is on Lync?Where is your voicemail?

For Pilots/transition: permanent forwarding okPBX phone permanently forwarded to new DID on Lync (admin set with user override)Easy to configure, limits user confusion while easing customer concernsTransition only – not a long term solution

Should your users really have 2 phones?

Recommended deployment: single system per user, homogeneous groups of users:

Designed for and fully supportedPredictability of experience (boss/admin, voice mail…)Reduces cost; economies of scale at the site/unit level; simpler support scenariosCan be achieved both with “PBX replacement” and with “PBX overlay with individual migration from phone to Lync”Important to keep groups of users (preferably sites) homogeneous

Pick one: belt or suspenders

RCC is still in Lync 2013 and supportedNo significant difference with Lync 2010 (March 2012 update)In Lync 2013, intended to facilitate migration of existing RCC customers to Enterprise Voice; not targeted at new RCC customers

RCC is outdated technologyProvides click-to-call using PBX handset using TR/87 (CSTA over SIP)Developed in 2004 with explicit goal to be a short term transition mechanism until Enterprise Voice, no notable improvement since, no new investmentPoor track record (cost, topologies, operations, user satisfaction); few successful deployment at scale ever; most customers migrated to Enterprise Voice

No interop program; CSTA GW partners exiting

RCC is not advisable

Technical toolkit

Feature that could change your technical strategyInter-trunk routing

Facilitate implementation and/or improve resiliencyCalling Number TranslationTrunk definition, M:N routingLots of useful “little things” (often with important consequences)

Using Pool FQDN instead of individual machine FQDN for cert & connection checkingFailover Routing and four second socket connection timer from MediationDNS Load Balancing Support outbound from Mediation to SIP peerDual Stack IPv4/IPv6 [unsupported: v6 on Mediation egress]Passing Referred-By and History-Info from Mediation to PeerResiliency enhancements for trunking – bidirectional OPTIONS, peer routing to backup pools

What has changed in Lync 2013

Supported: Lync 2010 Mediation with Lync 2013 poolFunctional at 2010 level of capabilityGreat for upgrading to Lync Server 2013 with minimal impact2013 Mediation needs to interoperate with 2013 qualified infrastructure

Timing: When will X be qualified with Lync 2013?Interop testing started when 2013 was released in OctoberVendors work to qualify in TekVizion & Wipro immediately Limited throughput for first six months of release

Internal PBX TestingFocused on back-level versions of Alcatel, Avaya, Cisco & SiemensStill in progress (lots in the pipeline, coming soon)….

Lagging Interop with Lync 2013

Voice Routing Coexistence

Home Server Mediation

Server

Lync Server 2013 Lync 2013 Lync 2013 Supported

Lync Server 2013 – Lync Server 2010

Lync 2013 Lync 2010 Supported

Lync 2010 Lync 2013 Supported

Lync Server 2013 – OCS 2007 R2

Lync 2013 OCS 2007 R2 Supported

OCS 2007 R2 Lync 2013 Not Supported

Mediation Server Next Hop Server Home Server

Lync Server 2013 Lync 2013 Lync 2013 Lync 2013 Supported

Lync Server 2013 – Lync Server 2010

Lync 2013 Lync 2013 Lync 2010 Supported

Lync 2010 Lync 2010 Lync 2013 Supported

Lync Server 2013 – OCS 2007 R2

Lync 2013 Lync 2013 OCS 2007 R2 Supported

OCS 2007 R2 OCS 2007 R2 Lync 2013 Supported

Outbound Calls

Inbound Calls

* Contents from 2010 SBA will write monitoring and archiving contents to Lync 2010 store** Assumed certified Gateways for the release of MS shown in the tables above

Lync 2010 PoolLync 2013

Preview Pool

Lync 2010 SBA

Supported Supported *

Lync 2013 SBA

Not Supported Supported

Survivable Branch Appliance

SIP based interoperability specification under the “Infrastructure” pillar of OIP(PSTN) gateways and SBAIP-PBXSession Border Controllers

Foundation for virtually all voice interoperabilityImportant to verify your peer is listed – but also any caveat

Direct SIP

New in 2013Provides basic session managementBasic call routing capabilities to, from and between downstream telephony systemsLeverages the Direct SIP program for Gateways and IP-PBX, applicable to all devices qualified in program

Facilitate migrationPosition Lync and its PSTN GW as primary, connecting the PBX via Lync

Use Lync as your toll bypass solution for existing PBXIP-network your existing PBX via and with Lync

Inter-trunk routing

Inter-trunk routing - migration

Inter-trunk routing – PBX networking

Media Bypass

OIPqualifiedIP-PBX

capable ofbypass

PBX end-points

Lync poolwith

MS role

Lync end-points

MediaSignaling

Direct SIP to IP-PBX with media bypass

Frees media from transiting via Mediation 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 supportedWhen client is not “local”, media goes through Mediation

Mediation provides audio healing

Enables “lightweight” MediationCollocation with FE, SBA

Media Bypass definition and benefits

PBX, IP-PBX, SBA or GW that supports bypassAll qualified SBA support bypassGW qualified at Lync level support bypassUnfortunately, few PBX or IP-PBX support bypass today (use SBC, GW if not)

Need a centralized media processing pointNo bypass direct to endpoint (phone) is supportedRequires a media aggregation point, e.g. Cisco’s Media Termination Point (MTP)

Not the simplest of topics…Skills on 2 systems; routing optimization; resiliency scenarios…For complex topologies, recommend an experienced partner

Media Bypass - what is required

Functional topology

CUCM + MTP1

Lync

Cisco8001

Lync8500

Lync8000

Cisco8501

MTP 2

WAN

Mediation

HQ Site Branch

WAN call between Lync in branch and Cisco phone via central MTP – no Bypass

CUCM

Lync

CiscoEndpoint

Lyncclient

Lyncclient

Ciscophone

ISR (MTP)

WAN

G.711

Mediation

Codec basedon CAC or RTT

HQ Site Branch

In-branch call between Lync endpoint and Cisco phone via branch MTP

CUCM

Lync

Mediation

CiscoEndpoint

LyncEndpoint

LyncEndpoint

WAN

Ciscophone

ISR (MTP)

G.711

HQ Site Branch

In-branch call between Lync endpoint and Cisco phone via branch MTP – WAN down, call stays up

CUCM

Lync

Mediation

CiscoEndpoint

LyncEndpoint

LyncEndpoint

WAN

Ciscophone

ISR (MTP)

G.711

Call stays up

HQ Site Atlanta Branch

IntroductionLync: interoperability by designLync - Skype federation

Voice interoperabilityPrinciples and technical strategy Technical toolkit: Direct SIP, SBC, Trunking, Media bypass…

Video interoperabilityTowards ubiquitous interop without transcoding

Agenda

Lync Video StrategyHigh quality video in every desktopHigh resolution at low costSingle client experienceIntegration with applications

Improve the meeting room experienceSimplify UX, better user experience will bring more adoptionIntegrate conference rooms into the Lync UC environment.Improve productivity

Embrace and lead interoperability Integrate customers’ existing environment to expand the reach and coverageSupport legacy devices through gatewaysDevelop on market standards and contribute to the success of UCIF

Video Qualification to dateHigh bar to ensure end-to-end experienceRegistering to Lync and directory, peer to peer calling, conference joinGreat media capability with Wideband Audio and HD Video supportSupporting remote users with Firewall Traversal, Signaling & Media Encryption

Video Teleconferencing (VTC) endpointsLifesize Team 220, Room 220*, Express 220*, Passport*Polycom HDX 4500, 6000, 7000 & 8000

Multipoint Conferencing Unit (MCU)Polycom RMX 2000 & 1500

Gateway Radvision SCOPIA Video Gateway for Microsoft Lync

* Qualified with 2007 R2

Lync 2010 Video Recap

Point-to-pointUp to HD 720p (enabled manually and quad-core CPU 30fps)Supported codecs are H.263 (CIF) or RTVideo (VGA->HD) Panoramic video (up to 1056×144, also available in multi-point)

Multi-pointSupported codec: RTVideo (up to VGA, based upon request where > 60% have capabilities)AVMCU is performing active speaker switching & rate matching (based on available client bandwidth)

Lync 2013 Video Improvements

Point-to-pointUp to HD 1080p (requiring dual-core CPU together with hardware acceleration)Supported codecs are RTVideo (up to HD 720p) or H.264 SVC (up to HD 1080p)Panoramic video (up to 1920x288, also available in multi-point)

Multi-pointSupported codecs are RTVideo (up to VGA) or H.264 SVC (up to 1080p)AVMCU can provide up to 5 active speakers (or manual selection), video cropping and rate matching

What about mobility?Lync 2010 MobileNo Voice/Video over IP experience

Windows 8/RT Modern UIPoint-to-point videoMulti-party video (Gallery View)Leveraging H.264 SVCH.264 encoding within ARM chipsets

Lync 2013 MobilePoint-to-point videoMulti-party video (single active speaker)Leveraging H.264 SVCH.264 encoding within ARM chipsets

Why H.264 SVC?ExperienceGallery View capability with a non-transcoding MCUDynamic layouts, by giving endpoints the ability to control their received videoHD 1080p 30fps video without the need for high-end processing, taking advantage of CPUs with Accelerated Processing Units (Intel Sandybridge, Ivybridge and AMD Fusion)

Standards-basedBased upon Unified Communications Interoperability Forum (UCIF) specification for video, transport and signallingBit stream compatible with other video conferencing vendorsReduced need for “heavy lifting” where interoperability is requiredRTVideo is a legacy codec, H.264 SVC is now preferred

Removing H.263 in Lync 2013

H.263 is a low quality codec w/ CIF quality video

Better alternative with H.264 AVC

Backwards compatibility is satisfied with RTVideo

In rare cases, partner solutions

H.264 Video CodecProvides another codec for traditional VTC and Telepresence to connectPartners will support H.264 and RTVideo in Lync 2013RTVideo is required for Lync 2010

Video enhancements in signalingTo take advantage, partners need additions in signalingChanges documented in Microsoft Office Protocols Documents

Unified Communications Interop Forum (UCIF)Continue work in UCIF for interoperability Partners will support same UCIF adopted UC mode 0 and UC mode 1

Video Interoperability Direction

Lync 2013 Interoperability Use CasesQualified SystemsH.264 SVC UCConfig Mode 1 and RTV SupportCentralized Conferencing Control Protocol SupportMultiparty Gallery view and Face Detection with Smart Framing

Compatible SystemsRequire updates to support changes in Lync signaling and transport protocolRTV is required as H.263 codec support droppedH.264 AVC or SVC interop possible

Standard SystemsNo native Microsoft protocol or codec supportNeed new gateway to provide signaling interop and H.264 and RTV video

Cisco Interoperability

Announced at Lync Conference

Make rich video more pervasive and accessible

Interoperability between Lync and Cisco VTCs

Video Interoperability Server forthcoming

Lync Server 2013 Interop

Lync 2013 Clients

Lync 2013 Server

StandardSystems

QualifiedSystems

QualifiedGateway

Signaling

Media

H.264 SVC

RTV

RTV

Qualified Systems

Compatible Systems

Option 1Option 2

StandardSystems

Option 1Option 2

H.264AVC

H.264 SVC / AVC

CompatibleSystems &

Clients

Peer-to-Peer Scenarios

H.264AVC

Lync Server 2013 Interop

Lync 2013 Client

Lync 2013 Server

StandardSystems

QualifiedSystem

QualifiedGateway

Signaling

Media

H.264 SVC

Qualified Systems

Compatible Systems

RTV Client Joins2013 Clients add RTV StreamStandardSystems

Media TranscodingMedia Relay

H.264 SVCH.264 SVC

CompatibleSystems &

Clients

+ RTV

RTV

+ RTV

Multiparty ScenariosRTV

H.264 AVC

Conclusion

Lync 2013 continues with deep commitment to interopScenarios, programs, documentationVoice scenarios enrichedIntertrunk routing

Video scenarios drastically expandedH.264 SVC, no/limited transcoding

Related contentOUC-B401 Dial Plan

OUC-B204 Network Design

msdn

Resources for Developers

http://microsoft.com/msdn

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources

Sessions on Demand

http://channel9.msdn.com/Events/TechEd

Resources for IT Professionals

http://microsoft.com/technet

Evaluate this session

Scan this QR code to evaluate this session.

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows 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.