Microsoft® Lync™ Server 2010The Voice StoryModule 03

Microsoft Corporation

Session Objectives• Provide an overview of Microsoft® Lync™ Server 2010 voice

investments• Understand Lync Server 2010 architectural components• Understand how Lync Server 2010 investments help lower

Total Cost of Ownership (TCO)• Understand core routing changes and media bypass• Understand PBX interoperability options

2

Agenda• Voice Investments overview• Voice Architecture overview• Media Bypass• Routing changes

• Caller ID controls• Route translations

• Analog Devices, Private line• Malicious Call Trace, Enhanced 9-1-1 (E9-1-1)• Interoperability• Summary

3

Voice Investments

4

• “Anywhere Access”• IM and Rich Presence• Common voice

features• Unified messaging• Audio and video

conferencing• Desktop integration

“OCS 2007”

“OCS 2007 R2”

Lync Server

• Single Number reach• Attendant Console• Delegation/TeamCall• Response Groups• Session Initiation Protocol

(SIP) Trunking• Dial-in audio conferencing• Higher definition video• UC Workflow activities

• Branch Resiliency (SBA)• Datacenter Resiliency• Call Admission Control • Call park, Unassigned #• Topology changes• Media bypass• Enhanced 9-1-1 for North

America (NA) • Routing changes• Analog devices• Common area phones• Private line • Malicious Call Trace (MCT)• Larger device portfolio

71%

17%

12%

Voice Investments

5

• Topology changes• Media bypass• Enhanced 9-1-1 for North

America (NA) • Routing changes• Analog devices• Common area phones• Private line • Malicious Call Trace (MCT)

This Session

Lync Server

Voice Topology: OCS 2007 R2 PIC

XMPP

MSNAOL

Yahoo

RemoteUsers

FederatedBusinesse

s

EdgeServices

Perimeter Network

Front End Back End

UC Endpoin

ts

Media gateway

UC Pool

Direct SIP

PSTN Med

iati

on

S

erv

ers

IP-PBX

ExUM

On-premise

ArchivingMonitoring

AD DNS

SIP Trunkin

g

CircuitPacket

6

Voice Topology: Lync Server 2010PIC

XMPP

MSNAOL

Yahoo

RemoteUsers

FederatedBusinesse

s

EdgeServices

Front End (incl. Mediation)

Back End

ExUM

UC Endpoin

ts

ArchivingMonitoring

AD DNS

Media gateway / SBA

On-premise or online

UC Pool

PSTNIP-PBX

SIP Trunkin

gDirect SIP

AV Conf.

Analog Devices

Mediation Server

CircuitPacket

7

Perimeter Network

Mediation Service Collocation• Multiple Gateways per Mediation Service

• Lync Server 2010 allows for Gateways to be connected to the same Mediation Service (N:1)

• Voice Routes point to a Gateway• Topology document used to find an

appropriate Mediation Service, inserted into the routing path

• Mediation Service uses the gateway fully qualified domain name (FQDN) in the Request-Uniform Resource Identifier (URI) to route to appropriate Gateway

• Multiple Mediation servers in a pool• Allows a certified Internet Protocol Public

Switched Telephone Network (IP-PSTN) gateway to load balance across a pool of Mediation Servers

OCS 2007 R2

Lync Server 2010Route gatewa

y

Route_US LAX_GW

Route_EURDE_GW1

DE_GW2

Route_APAC

SYD_GW

Route gateway

Route_US LAX_GW

Route_EURDE_GW1

DE_GW2

Route_APAC SYD_GW

8

Media Bypass

• Lync Server 2010 introduces media bypass of the Mediation Server:• In Lync Server 2010, whenever possible, media will flow

directly to gateway without traversing Mediation Server• Signaling continues to traverse Mediation Server role

• Key scenarios:• Bypass to a media gateway• Bypass to select IP-PBX (may require Media Termination

Point)

9

Media Bypass – Main Benefits• Consolidation of most Microsoft resources on Front End and/or at

Data Center:• Topology simplification:• TCO: greatly reduces total number of servers

• Simplify interop with Internet Protocol private branch exchange (IP-PBX):• Keep in-branch media between IP-PBX and Lync 2010 local without

deploying Mediation Server on site

• Optimize media flow and Quality of Experience (QoE):• Eliminate unnecessary hops and potential points of failure• Save bandwidth across wide-area network (WAN) by not hair-pinning• Improve voice quality

10

Media BypassExample Topologies

1. PSTN Call from Main site via Gateway with bypass2. PSTN Call from Branch via existing IP-PBX with bypass3. PSTN Call from Branch via Gateway4. PSTN Call from Main Site & Branch Office using Centralized SIP Trunking5. PSTN Call with CAC rerouting through Branch PSTN Connection6. Main site call with Lync Server 2010 endpoint & PBX endpoint via Main

PBX7. Branch call between Lync Server 2010 endpoint & PBX endpoint via

Branch PBX8. Branch call between Lync Server 2010 endpoint & PBX endpoint via

Main PBX

11

Media BypassExample Topologies

Main Site(with Data Center)

IP-PBX

Lync Server

Mediation

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

GW / SBA

PBXEndpoint

IP-PBX

Mediation shown here standalone for clarity

Can also be collocated in the pool

12

Lync 2010Endpoint

Media BypassPSTN Call from Main Site via Gateway

Main Site(with Data Center)

IP-PBX

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

GW / SBA

PBXEndpoint

IP-PBXG.711

Lync Server

Mediation

13

Lync 2010Endpoint

Media BypassPSTN Call from Branch via existing IP-PBX

Main Site(with Data Center)

IP-PBX

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

PBXEndpoint

IP-PBX

G.711

Lync Server

Mediation

14

Lync 2010Endpoint

Media BypassPSTN Call from Branch via Gateway

Main Site(with Data Center)

IP-PBX

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

GW / SBA

PBXEndpoint

IP-PBX

G.711

Lync Server

Mediation

15

Lync 2010Endpoint

Media BypassPSTN Call from Main Site & Branch Office using Centralized SIP Trunking

Main Site(with Data Center)

GW / SBA

IP-PBX

PSTNPBXEndpoint

Branch Site

PBXEndpoint

IP-PBX

Lync 2010Endpoint

WAN

SIP Trunking

G.711

G.711

RT Audio Narrowband

Lync Server

Mediation

16

Lync 2010Endpoint

Media BypassPSTN Call with CAC Rerouting through Branch PSTN Connection

Main Site(with Data Center)

GW / SBA

IP-PBX

PSTNPBXEndpoint

Branch Site

PBXEndpoint

IP-PBX

Lync 2010Endpoint

WAN

SIP Trunking

G.711

Lync Server

Mediation

17

Lync 2010Endpoint

Media BypassMain site call with Lync Server endpoint & PBX endpoint via Main PBX

Main Site(with Data Center)

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

GW / SBA

PBXEndpoint

IP-PBX

IP-PBX

G.711

Lync Server

Mediation

18

Lync 2010Endpoint

Media BypassBranch call between Lync Server endpoint & PBX endpoint via Branch PBX

Main Site(with Data Center)

IP-PBX

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

WAN

G.711

Lync Server

Mediation

19

IP-PBX

PBXEndpoint

Lync 2010Endpoint

Media BypassBranch call between Lync Server endpoint & PBX endpoint via Main PBX

Main Site(with Data Center)

PSTNPBXEndpoint

Branch Site

Lync 2010Endpoint

Gateway

PBXEndpoint

IP-PBX

WAN

G.711

RT Audio Narrowband

Lync Server

Mediation

20

IP-PBXLync 2010Endpoint

Caller ID Presentation Controls• Admins can natively control what Caller ID is presented to receiving

party (PSTN/PBX):

• Per user/group controls to suppress/alter calling party number

• Granular controls based on caller and destination number:• Alice calls an external PSTN number, caller ID is presented as +1 425 555 0100

• Alice calls an internal PBX number, caller ID is presented as +1 425 555 2302

• Override for “simultaneous ringing”:Bob calls Alice, who has simultaneous ringing configured to her mobile number; Bob’s caller ID is presented

• Calling Name Display feature allows display name to flow to/from OCS (also in OCS 2007 R2 CU)

21

Configuring Caller ID

22

Voice Routing EnhancementsCentrally manage number formatting prior to routing to PBX/PSTN• Alice calls +44221234567;

based on route translation pattern, called number formatted to 01144221234567 when using gateway in Redmond

• Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using gateway in London

23

Voice Routing EnhancementsCentrally manage number formatting prior to routing to PBX/PSTN• Alice calls +44221234567;

based on route translation pattern, called number formatted to 01144221234567 when using gateway in Redmond

• Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using gateway in London 24

Voice Routing EnhancementsCentrally manage number formatting prior to routing to PBX/PSTN• Alice calls

+44221234567; based on route translation pattern, called number formatted to 01144221234567 when using gateway in Redmond

• Alice calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using gateway in London

25

Enhanced Voice Policies

• Provide admins flexibility to control user voice entitlements

• Useful to address Common Area Device requirements

26

Analog Phone Device Management• Physical connectivity of Analog devices provided by gateway partners• All routing and policy enforcement for Analog devices centralized in Lync Server 2010

– eliminates the need to manage gateways as “mini-PBX”• Certificate Services (CS) Call Detail Record (CDR) infrastructure used to track usage

27

PSTN

Lync Server

Signaling

Media

Gateway Analog

Device

ATA

Analog Device

Analog Fax Device Management• Physical connectivity of FAX devices provided by gateway partners• All routing and policy enforcement for FAX devices centralized in Lync Server 2010 –

eliminates the need to manage gateways as “mini-PBX”• Certificate Services (CS) Call Detail Record (CDR) infrastructure used to track usage • Optimized routing to allow Fax calls routing through Lync Server 2010 without

terminating Media

28

Fax

PSTN

Lync Server

Signaling

Media

Gateway

ATA

Fax

Private LineLync Server 2010 introduces support for private line

• Single SIP URI, single Exchange mailbox, single presence source• Receipt of inbound calls on private Direct Inward Dialing (DID) to

same Session Initiation Protocol (SIP) URI• Private telephone lines are available for on-premises deployments

onlyPrivate lines carry many of the same features

• Call pickup & park work as expected• Simultaneous ringing & call deflection on primary line carry to

private linePrivate lines are different:

• Available for inbound calls only• Overrides delegation, call forwarding, do-not-disturb and other

routing options – private calls are always going to go through• Calls to a private line have a distinctive ring & “toast” pop-up

29

Malicious Call Trace

• Lync Server 2010 provides the end-user the capability of tagging the prior call as a malicious call

• Supported in Lync 2010, Lync 2010 Phone Edition & Attendant Console

• Tagging is reflected in the backend CDR database, enabling the Lync Server 2010 administrator to take action on the call

30

Enhanced 9-1-1Design requirements and goals for Lync Server 2010• Base requirement – provide location with emergency calls

• The dispatchers must know the civic/street address of the caller

• Locations may need to be to specific building, floor, wing, office, etc.

• Support the roaming nature of Lync Server 2010 users• Inside the network – automatic or manual• Outside the network – first manual then automatic for

frequent locations• Connecting to the appropriate authorities without having

a PSTN gateway for each emergency network location31

Enhanced 9-1-1Location Infrastructure• Enablement location provides flexible deployment

• “Network Sites” – definition of where E9-1-1 services are available• Users – E9-1-1 enablement available through user policy

• Location Information Server (LIS) added to Lync Server 2010 Web components

• Locations can be based on subnet, switch, port, Wi-Fi access point, and are updated on each client registration or network change

Partner Components• Emergency signaling and location conveyed from client via

SIP trunks to 3rd party partner for Public Safety Answering Point (PSAP) routing

• Connexion and Intrado have announced routing services• Based on National Emergency Number Association i2 architecture

32

PBX InteroperabilityFor Customers Not Ready to Replace PBX

• VOICE• Lync Server 2010 voice networks with any PBX• Direct SIP for signaling • G.711 and other standard codecs

• CONFERENCING• Lync Server 2010 conferencing connects to any PBX• Direct SIP for signaling • G.711 and other standard codecs

• PRESENCE• Lync Server 2010 presence is available to any PBX• SIP verbs to get and set presence

33

Direct SIPLync PBX

CONFERENCING

Direct SIPLync PBX

VOICE

SIP get and set

PRESENCE

Lync 2010 user PBX user

PBX user with Lync conf

Lync PBX

PBX user with Lync IM/P

PBX phone automatically called upon meeting join

PBX InteroperabilityStreamlining Unified Conferencing for PBX phone users

34

1. Full Unified Communications (UC) with legacy phone elimination

Lync Server 2010 connects to PSTN or PBX via SIP Trunking, Direct SIP or gateway. User’s DID homed on Lync Server 2010, user provided with optimized device

2. Full UC with legacy phone left in place for transition period

Same as above, but with the PBX phone left in place for transition, often with Simultaneous ringing used to have both Lync Server 2010 and PBX phone ring

3. Legacy phone with OCS unified conferencing

Lync Server 2010 connects to existing PBX systems via Direct SIP or SIP/PSTN gateway. Lync 2010 allows user to “Join From” their PBX phone when in audio conferences

4. “Click-to-Call” with legacy phone via Lync Server 2010

Lync Server 2010 integrates with existing PBX systems using Click-to-Call capability. Conferencing join through dial-in or “click-to-join” with multipoint control unit (MCU) dial-out

5. PBX manufacturer plug-in to Lync Server 2010

Software built on Microsoft’s UC development platform provided by PBX manufacturer is deployed on all user desktops alongside Lync 2010

PBX InteroperabilityOptions for Customers

35

Summary: Key Voice Changes• Resilient and always available

• Caller ID presentation controls• Selectively exposing Calling Party Number

• Passing Calling Party Name (in/outbound)

• Routing enhancements• Centrally managing called party number formatting without relying on gateway

• Mediation server 1:N to gateway

• Enriched voice policies

• Centralized management of analog lines

• Mediation server Media bypass• Remove most/all dedicated Mediation Server boxes from topology

• Keep media local to the site, avoid/limit tromboning

• Locally exchange media with IP-PBX without any incremental hardware on site 36

Summary: Key Benefits• PBX feature parity/completeness

• Analog lines• Calling ID management

• Management simplification/centralization• Routing enhancements from local gateway management to centralized management

• Facilitating full scale deployments• Topology simplification (media bypass)• Centralized management of Analog devices

• TCO reduction• Less physical boxes• Centralized management• Better user facing capabilities with respect to QoE

• Interoperability• Improved interoperability options

37

38

Q&A

© 2011 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.  This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED  OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.