Jamie Stark Mitchelle GonsalvesProduct Manager Program Manager

Voice Interoperability Overview

VOICE306

Fill out evaluations to win prizesFill out evaluations on MyLync or MyLync Mobile.Prizes awarded daily.

Goals

Microsoft’s interoperability investments

Latest on practical voice interop programs

Voice Deployment Topologies

Interop Investments

Invest in Interoperability across three dimensionsIndustry Alliances – UCI Forum, OVCC, ONF, Wi-Fi AllianceProtocol documentation – Office Protocol DocsScale programs – UC Open Interoperability Program (technet.microsoft.com/UCOIP)

Lync designed for interoperabilityFrom Planning through Spec, Dev, Test and Sustained EngineeringInteroperability scenarios persist across releases to protect customer investment

Interop functionally the lead for deploymentsWork with what enterprises have todayExpect a heterogeneous future

Interoperability with Lync

Office Protocol Documentation

Every communication between Clients & ServersWhen clients exchange data with servers, we document and publish the protocol used.This occurs across all Microsoft Office applications – from PowerPoint to Exchange to Lync.

Refers back to the core industry standardsIncludes Session Initiation Protocol (RFC 3261), Real-time Transport Protocol (RFC 3550), and many more.Many instances here where to core standard is implemented and extended to support Lync capability.

Intended for product developmentThese aren’t practical for enterprise customer deployment

http://msdn.microsoft.com/en-us/library/cc307432(v=office.12).aspx

For example….

Interop Programs

Open Interoperability Program - ObjectivesEnsure high quality interoperability of infrastructure devices for voice interop in Lync deployments

Build an ecosystem of Lync interoperable vendors and devices

Provide customers wide choice of vendors and price points

Enable deployments in various geographic locations

Enable deployments in competing customer environments

UCOIP - Categories

Applications ISV Qualifications for Third Party Applications

Devices Phones, Headsets, USB Handsets, etc.

Infrastructure IP PBXs, Gateways, Survivable Branch Appliances, Session Border Controllers,

Load balancers, Reverse Proxy & Networking

Online Dedicated Lync On-premise solution hosted by Microsoft for large customers

Services SIP Trunks used on premise & for O365 Dedicated & E911 Routing

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

Infrastructure Device Description

Qualified IP PBXs and Gateways

Used for direct connectivity to the PSTN via a PRI line

Supported IP PBXs Supported: Legacy IP-PBXs internally tested with caveats

Survivable Branch Appliances

Lync Server with Gateway bundled for WAN branch survivability

Session Border Controllers Used for connectivity between Lync deployments and SIP trunk providers

Reverse Proxies Required for external clients to access Lync web services running on user’s home pool

Load Balancers Used for load balancing http connections to Lync Web services

Networking Wired and Wi-Fi Network Infrastructure

VDI Thin Clients running in a VDI environment

Program Enhancements in FY14 FY13 FY14

No third party support while working on support case

Enhancement: Providing partner training to PSSto Enhance Customer support Status: Delivered 4 depth partner trainings

Minimal interaction with competing PBX vendors

Enhancement: Leveraging strategic relationships with legacy PBX vendors to add additional supported PBXsStatus: 2 legacy PBXs qualified

Limited interaction with customer support

Enhancement: Monitoring support issues and identifying gaps in testStatus: 10 new tests added across programs

No qualified Reverse Proxy Enhancement: Added qualification program for reverse proxiesStatus: 3 Reverse Proxies qualified

Qualification Activity in FY14Qualified Device Partner Model

Feb 14, 2014 Gateway Sonus SBC 1000

Feb 14, 2014 E-SBC Sonus SBC 1000

Feb 6, 2014 IP-PBX NEC UG30

Feb 5, 2014 IP-PBX Aastra Aastra 470

Dec, 10, 2013

E-SBC Oracle ACME Net-Net OSVM

Dec 3, 2013 E-SBC Sonus VX 1200

Dec 3, 2013 Gateway Sonus VX 1200

Nov 19, 2013

Reverse Proxy F5 Big IP LTM

Nov 15, 2013

Gateway Audiocodes M500

Nov 15, 2013

Gateway Audiocodes M2000

Nov 15, 2013

Gateway Audiocodes M3000

Nov 11, 2013

IP-PBX Aastra MX One

Nov 8, 2013 Gateway Audiocodes M800

Q4 FY13 Q1 FY14 Q2 FY14 Q3 FY140

5

10

15

20

25

30

35

40

45

50Count of Partner SKUs Quali-

fied

Partner Facing Enhancements in FY14

FY 13 FY14

Redundant / ambiguous test cases increased time to qualify

Enhancement: Reduced Qualification time by removing 9% of the cases across the programs

Bugs in automation tool slowed down qualification

Enhancement: Added15 bug fixes to reduce time to qualify Maintained 84% automation Improved documentation of known issues

with workarounds

10-15% reduction in total time to qualify

Legacy IP PBX Interop Status

Supported: CUCM 7.0.1, Avaya SM 6.1

In Progress: Some of the more recent IP PBX versions

Next Steps: Working with the vendors to get these issues resolved

Lync 2013 Infrastructure Partner Ecosystem

Topologies

Typical enterprise starting pointStrong PBX presence; Concern about Lync Voice viabilityPSTN Termination at the Legacy PBXExisting numbering planTypical dialing habits that originate from the PBXClass of Service that define allowed destinations

PBX team wants to connect Lync to the PBXShould you?Why? Why not?An Important choice to make

Connecting to the PSTN

Existing PBX

Existing Phone Handsets

Numbering Plan

+31-20-500 1000 to+31-20-500 1999

4 digit Internal extensions 9 for an outside line3 digits + extension for other locations…..

Dialing Habits

No premiumLocal, NationalInternational

No premiumLocal, National

Class of Service

PSTN

Class of Service

Connect to the PSTN (parallel to IP-PBX)

Lync 2013Existing

PBX

PSTNWhy?Easy and fastNo additional PBX investments & configLync session management can mitigate some of the disadvantages.

Why Not?New numbers for the end-userHow about internal calling?Need additional trunk capacityMigrating a user = changes at the Provider

Use qualified gatewaysA gateway is a physical device that connects two incompatible networksA gateway translates signaling and media between Lync and the PSTNAllows gateway to act as B2BUA/transcoding resource for calls between Lync Server 2013 and the PSTN

Circuit / TDM Trunking benefitsMore broadly understoodNo WAN dependencyLocal carrier choiceBranch resiliency

Connecting to the PSTN via gateway

SIP SIP

LyncMediation Server

LyncPool

PSTN

QualifiedGateway

SIP Trunking / IP Telephony Service ProvidersCarrier provides telephony service for enterprises exclusively over SIP, no circuits required.Available since OCS 2007 R2 – works either direct from Mediation or through CPE SBC.Service includes DIDs and/or number portability for migrations from other SPs.Customers get CapEx benefits in cost per call and OpEx benefits in management.

Demand for SIP Trunking continues to grow

Connecting to the PSTN via SIP trunk

SIP

LyncPool

LyncMediation Server

PSTN

SoftSwitch -or-PSTN Gateway

SIP

VPNRouter

VPNRouter

SIP

SBCSession Border Controller

VPN Tunnel

Enterprise Network Service Provider Network

Sizing PSTN Trunks

For replacement, existing call volume is knownHowever, account for new behaviorsInclude simultaneous ringing requirementsCalculate for PSTN conferencing

Erlang B calculations when appropriateFor new features (such as dial-in audio conferencing) Erlang calculator provided in Bandwidth Planning Tool

23 23

Connect to the PBX

Existing PBX

Lync Server 2013

PSTNWhy?That is what we always doPBX owns number planUser can keep own numberInternal calling at no costBenefit from existing PBX infrastructureBenefit from existing trunk capacity

Why Not?PBX Dependencies Additional PBX costRequires PBX configurationWhat happens when migration is done?Migrating a user = changes in the PBX

Connecting to the PBXDirect SIPOnly for qualified or tested IP-PBXsProvides voice capabilities between endpoints on either call control serverAllows endpoints on both sides to utilize features on the other call control serverSimplest method of interoperability, relying on standard SIP protocols

Via a GatewayUse supported gatewaysUse gateway as intermediary in scenarios such as SIP to TDM, or to nonqualified third-partyAllows gateway to act as transcoding resource for calls between Lync & and third party

PSTN SIP SIP

LyncMediation Server

LyncPool

QualifiedIP-PBX

SIP SIP

LyncMediation Server

LyncPool

TDM PBX

PSTN

QualifiedGateway

Direct SIP: Trunk DefinitionA TrunkMediation FQDNMediation SIP listening portGateway FQDNGateway SIP listening port

Provides forBetter interworking with IP-PBXs for

bypassTLS/SRTP capability for multiple SIP

trunks to the same SBC FQDNFlexibility - when OBR matches a DN to a

route, route consists of a list of trunks

26

Direct SIP: Trunk DefinitionA TrunkMediation FQDNMediation SIP listening portGateway FQDNGateway SIP listening port

Provides forBetter interworking with IP-PBXs for

bypassTLS/SRTP capability for multiple SIP

trunks to the same SBC FQDNFlexibility - when OBR matches a DN to a

route, route consists of a list of trunks Lync Pool

Site 01Mediation Pool

SBCsbc1.provider.com

Site 02Mediation Pool

Trunk 1 Trunk 2

PSTN

MPLS

Gateway F connects to two Mediation servers, and can be within a site or across sitesA single Mediation Server listening port is needed for trunks to multiple gatewaysResiliency does not require multiple Mediation Server listening ports

Port C : 5061, can be used as the Mediation Server listening port for Gateway 1 and Gateway 2Port D : 5068 can be used on SAME Mediation Server for a different gateway or IP-PBX if required

Direct SIP: Trunk DefinitionMediation Server C

Gateway F

Port A Port BTrunk 1

Port C

Port B

Trunk 2

Port C Port ETrunk 3

Mediation Server D

Gateway G

28

PSTN GatewayFQDN F

PSTN GatewayFQDN G

Direct SIP: IP-PBX Trunking

Associate Mediation Servers with PSTN Egress

Multiple trunks between a Mediation Server & PSTN gateway can be defined to represent IP-PBX SIP termination

Each trunk associated with the appropriate route for outbound calls from Mediation to IP-PBX

For inbound calls, per-trunk policy will be applied

Trunk config scoped globally or per trunk; similarly, dial plan can be scoped per trunk

Representative Media IP is a per-trunk parameter

Mediation Server

IP-PBX

Port A Port A1Trunk 1

Port B Port B1Trunk 2

Port n Port n1Trunk n

Direct SIP: IP-PBX Trunking

Keep media local Use MTPs on same site as Lync ClientEnable Media Bypass

ConfigurationDefine PBX-10 as PSTN Gateway.Use MTP1 as Alternate Media IP-AddressAdd Additional trunks for remaining MTPsUse Different PBX Listening portsDefine RepresentativeMediaIP for each MTP/Trunk

PBX-10

PBX Extension

PBX Extension

MTP-2

MED-10

Trunk 1MED-10<->PBX-

10PBX-10 port

: 5060Signaling IP: PBX-1Media IP : MTP-1

Trunk 2MED-10<->PBX-

10PBX-10 port

: 5061Signaling IP: PBX-1Media IP :

Media Bypass

Media Bypass

MTP-1

PSTN Gateway

PBX-10

MTP-2

50605061

Call routing from incoming trunk to outgoing trunkSet of PSTN usages associated on an incoming trunk to determine call route to an outgoing trunk.Provides better integration with additional scenarios to Lync qualified infrastructure.

Completely integrated into Lync routingExisting route configuration concepts keeps configuration familiar for administrator.Media bypass in inter-trunk routing calls is supported.Includes appropriate trunk-level authorizations, CDRs, etc.

Flexibly enabling routing paths including:Incoming PSTN calls to a PBX system via Lync.Outgoing PBX calls to a PSTN network via Lync.Outgoing PBX calls to another PBX system via Lync.

Session Management

Session Management

IP-PBX to PSTNIncoming call from the PBX trunkValidate incoming trunk associated PSTN usagesDetermine a routeApply outbound translation rulesRoute to outgoing gateway trunk

IP-PBX

Gateway

MediationServer

PBX User

Front EndServer

Trunk

Inbound Trunk

PSTN Usage

Route Outbound Trunk

Media

Trunk

PSTNMediationServer

Session Management

Between IP-PBXsIncoming call from the PBX trunkValidate incoming trunk associated PSTN usagesDetermine a routeApply outbound translation rulesRoute to outgoing PBX station

IP-PBX IP-PBXMediationServer

MediationServer

PBX User PBX User

Front-EndServer

Trunk Trunk

Inbound Trunk

PSTN Usage

Route Outbound Trunk

Media

Calling Number Translation

RouteRedmond-PBX

Outbound TrunkRedmond-PBX

An administrator can associate a set of translation rules to a trunk configuration to enable calling number manipulation

A trunk to route the call is determined based on the user voice policy and destination number

From the trunk configuration, a translation rule is applied for the calling number

PSTN UsageRedmond-PBX

Inbound Trunk

Called # Trans.Calling #

Trans. Route call

IP-PBX

Gateway

MediationServer

PBX User

Front EndServer

Trunk

Media

Trunk

PSTNMediationServer

Inter-trunk routing: PSTN to PBX user call

Which Model? Yes.

Existing PBX

Lync Server 2013

PSTN

Lync Server 2013ExistingPBX

PSTN

Summary

Microsoft’s interoperability investments

Latest on practical voice interop programs

Voice Deployment Topologies

Microsoft PavilionDemos, Speakers, Demos, Lync Room System, Experts, Demos, a Bar....and more Demos

ATTENDEE PARTYWednesday, February 19th

6:30pm-9:30pmHakkasan, MGM Grand

Brought to you by

When it comes to Vegas nightclubs, it doesn’t get any hotter than Hakkasan. And when it comes to opportunities to connect and reasons to party, no one does it better than Lync Conference! Our attendee party has a full lineup: an open bar, awesome food, and one of the best DJs that Vegas has to offer. Don’t miss out on the fun—stop by at 6:30pm and kick off and evening to remember. Come together.

HANDS-ON LABS

You can also access labs on MyLync!

3:00pm – 9:00pm10:30am – 9:00pm7:30am – 9:00pm8:00am –1:30pm

LOCATIONPinyon 3

Monday, February 17Tuesday, February 18Wednesday, February 19 Thursday, February 20

LRS

LOCATIONCopperleaf 12

Wednesday, February 198:30am – 9:45am10:15am – 11:30am1:00pm – 2:15pm2:45pm – 4:00pm4:30pm – 5:45pm

Thursday, February 209:00am – 10:15am10:45am – 12:15pm12:45pm – 2:00pm

MyLync allows you to create a custom experience and network with the Lync Community both online and in person.With MyLync, you can:• Build your own personalized calendar while browsing all available sessions• View breakout session material including PPTs and Videos within

48 hours of each session• Participate in the Community and find people in your social networks

who are attending and interact with speakers• Arrange meetings or social activities• Navigate the Exhibit Hall floor plan and learn more about our Sponsors• Fill out evaluations to win prizes

Log into MyLync at http://mylync.lyncconf.comFor MyLync support, please visit the Registration Desk.*

* Please note that adding a session to your calendar does not reserve a seat. Seating is on a first-come, first-served basis.

Birds of a FeatherBirds of a Feather flock together! Join daily breakfast discussions of relevant topics by sitting in the separately designated areas of the Meal Hall. Seating will be sorted in a different way for each Birds of a Feather breakfast:Wednesday, February 19:Where are you from? Asia/Pacific, Eastern & Central Europe, Latin America, Middle East & Africa, US (West, Central & East) and Canada, Western Europe

Thursday, February 20:What is your interest?Best Practices, Business Value, Clients & Mobility, Lync Meetings and Video, Lync Online, Networking, Platform, Server & Manageability, Voice

Fill out evaluations to win prizesFill out evaluations on MyLync or MyLync Mobile.Prizes awarded daily.

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