/
Planning Voice Deployments Planning Voice Deployments

Planning Voice Deployments - PowerPoint Presentation

yoshiko-marsland
yoshiko-marsland . @yoshiko-marsland
Follow
453 views
Uploaded On 2016-03-18

Planning Voice Deployments - PPT Presentation

Subbu Chandrasekaran Senior Program Manager Microsoft Corporation EXL410 Agenda Review Lync 2010 Topology Planning for Lync 2010 features Reference Architecture High Availability and Resiliency ID: 261319

media lync pbx bypass lync media bypass pbx branch 2010 site server pstn interoperability interop video edition mediation resiliency

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Planning Voice Deployments" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Planning Voice Deployments

Subbu ChandrasekaranSenior Program ManagerMicrosoft Corporation

EXL410Slide2

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide3

Takeaways

How to deployment enterprise voice in Greenfield environment How to enable Interop with existing

PBXSlide4

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide5

Voice Topology:

Lync

2010

PIC

XMPP

MSN

AOL

Yahoo

Remote

Users

Federated

Businesses

Edge

Services

DMZ

Front End (incl. Mediation)

Back End

ExUM

UC Endpoints

Archiving

Monitoring

AD

DNS

Media

GW / SBA

On-premise

or online

UC Pool

PSTN

IP-PBX

SIP

Trunking

AV Conf.

Analog Devices

Mediation Server

Circuit

PacketSlide6

Voice Resiliency Architecture

Backup

Registrar

Pool

Bob’s Primary Registrar &

User

Services:

EE

Pool 1

Data Center - EE Pool 1

Presence

Conferencing

Registrar

(Registration

& Routing)

AD & DNS

Alice’s Primary Registrar &

User

Services:

EE

Pool

2

Data Center - EE Pool 2

Presence

Conferencing

Registrar

(Registration

& Routing)

AD & DNS

Registrar

Survivable Branch Appliance

Branch Office

Joe’s Primary Registrar:

SBA

User Services:

EE

Pool 1Slide7

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide8

Location and Enhanced 911

Uses LIS

(Location Information Server )Location used for Presence, Emergency Routing

, or both

LIS

database Contains):

Wireless Access Point (BSSID)

LLDP Port

LLDP Switch

Subnet

MAC

Location Policy

used for E911 and routing

User

Subnet

E911 provided through Emergency Service Provider

Include

Security Desk IM

and conference

Outside United States; use location based emergency routingSlide9

Voice

Routing – Trunk Translations

Centrally manage number formatting prior to routing to PBX/PSTNAlice calls London using Redmond

+44221234567

01144221234567

Alice calls London using

London GW

+44221234567

0221234567 Slide10

Caller ID Presentation Controls

Natively control Caller ID presented to PSTN/PBX:

Granular controls based on callers and destination number:

Alice to external PSTN number

,

+1 425 707 9050

+1 425 882 8080

Alice to internal PBX number

,

+1 425 707 9050

+1 425 707 9050

Controlled by PSTN usage

Overrides “simultaneous ringing”

:

Bob calls Alice; Bob has masking for external calls & also has simultaneous ringing

Bob’s caller-id is presented to Alice’s mobile deviceSlide11

Exchange Unified Messaging (UM)

The Only supported voice mail solution

Support for Exchange UM 2007 SP1 and newerCo-locate UM and Mailbox serversMAPI traffic is less tolerant of latency than VoIP in this scenarioUM and Lync in separate forests is supported

Just ensure the EUM settings in the user objects are synched to

Lync

forest

Exchange Online and

OnPrem

together?

Yes

Turn on EUM enablement setting on the user object

User Move

Lync

Powershell

Edge Server is required to be deployedSlide12

And much more…

Response Group ServiceCall Park Service Private lineCall controls such as call forwarding,

simul-ring, transferDelegate, Team CallAnnouncement serverUnassigned numbersCommon area phones Call Admission ControlSlide13

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide14

UM

SCOM

Standard Edition

Enterprise Edition

Topologies

Director

Archiving

Monitoring

Mediation

Group Chat

Optional Servers

Front end

Back end

AV Conf

Edge

Servers

Topologies SimplifiedSlide15

Deployment Model

Global Deployment is a collection of Sites

Sites are made of PoolsPools host users & services (such as conferencing, Voice over Internet Protocol (VoIP))Slide16

Central Site

Small or Trial Deploy

Single

Data Center

Multiple Data Centers

Branch Office Site

Smaller organizations not requiring resiliency can choose a

Standard Edition Server (SE),

a single server with all roles consolidated on that server

functioning

Organizations who need resiliency will choose an

Enterprise Edition Pool (EE),

defining a pool of multiple servers comprised of front end and back end roles

“Paired” Standard Edition

can offer failover between two SE servers for lower cost and reduced functionality

.

Additional Server roles required include Archiving, Director, Edge and

Monitoring

Branches without redundant WANs will purchase a

Survivable Branch Appliance

to handle voice resiliency in the branch

office

Branches with a redundant WAN connection, still require basic PSTN termination with SIP Gateway.Standard Edition Server can be utilized for improved Quality of Experience (QoE) in large, distant “branches” (truly a Central Site) with lots of conferencing utilization

.Not all branches will require resiliency – for smaller branches, use Remote User Connectivity over public internet or 3G/4G network.

Typical Use

Departmental deployment of reduced criticality and scale

Enterprise deployments where multi-site high-availability is not a requirement

Huge deployments of a geographically dispersed workforce

Central Site

Central Site has a Standard Edition Server

Single Central Site with an Enterprise Edition Pool

Multiple Central Sites of Enterprise Edition Pools

Branch Office SiteBranch Offices for Survivability or PSTN interconnect

Branch Offices for Survivability or Public Switched Telephone Network (PSTN) interconnect

Branch will be combination of SE, SBA and PSTN-only

Pool-level Resiliency

Multi-site Resiliency

Sites that do not host a pool

Sites which host a pool of either SE or EE

Deployment OptionsSlide17

Reference Topologies

Small

Standard Edition central site

Branch through Edge

Small with Branches

250-5,000

Standard Edition central site

Single branch, with SBA

Small with Failover

Two Standard Editions -

“Paired” Standard Edition to support inexpensive failover

Any

Small

< 5000 users

This example

5,000 users, 3 servers

1667 users/serverSlide18

Reference Topologies

Single DC

Enterprise Edition, Single Data Center

Branch through Edge

DC with Branches

1,000 – 30,000

Enterprise Edition, Single Data Center

Two branches, one SBA, one PSTN Interconnect

Single Datacenter

< 100,000 users

This example

20,000 users, HA, 14 servers

1429 users/serverSlide19

Reference Topologies

Global

10,000 +

Two Data Centers with EE

One

Central Site with an SE

Some SBA

Some

PSTN

Very Large

Unlimited

Enterprise

Edition, > Two Data Centers

Standard

Editions

Survivable Branch

Appliances

Branch with

Standard Edition

Global,

Multi-Site

Unlimited

This example

Site 1: 18 servers

Site 2: 11 servers

Site3: 1 server

2413 users/server

Site B

Site CSlide20

Survivable Branch Appliance (SBA)

A purpose-built appliance optimized to provide resilient multi-modal communication for maximizing branch office user productivity. Solution re-architected for Registrar to work when

UserServices role is unavailable or unaccessible.

PSTN

WAN

Data Center

CS

Pool

Edge

Server

SBA

Branch Office

Components

Functionality

Go-To

Market

Windows Server® 2008 R2

Mediation Server

Registrar

PSTN Gateway

Normal/Failover mode

SIP Registrar

SIP Proxy and Routing engine

PSTN connectivity

Voicemail routing

PSTN re-routing

Centrally provisioned

Up to 1000 user support

OEM (Embedded channel)

5

partners

Audiocodes

HP

Dialogic

NET

FerrariSlide21

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide22

IP-PBX Interoperability

Pain

points

in

OCS 2007 R2

Interoperability via Direct SIP (OIP qualification)

Very broad range of PSTN gateways, Direct SIP to IP-PBX

R2 Direct SIP requires routing media through Mediation Server

Not a significant problem for central sites

But difficult in branches:

Requires Mediation

S

ervers in branches and/or

Media

tromboning

(hairpin through the WAN to Mediation Server in central site)Slide23

OIP

qualified

IP-PBX

PBX end-points

OCS pool

OCS end-points

Mediation

Server

Media

Signaling

IP-PBX

Interoperability

in

OCS 2007 R2

Direct SIP to IP-PBXSlide24

Removes need for media transit

Signaling

continues to transit through MediationB2BUA: security

demarc

,

interop

Media goes

direct

3 Advantages + media resiliency

Based on location of Media endpoints

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

Codec optimized for WAN using per session CAC;

Mediation provides audio healing

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

Lync 2010: Media BypassSlide25

OIP-

Qualified

IP-PBX

capable of bypass

PBX end-points

Lync pool

with

Mediation

Server

Lync

end-points

Media

Signaling

IP-PBX Interoperability in

Lync

Direct SIP to IP-PBX with media bypassSlide26

“Always Bypass” in “Global Settings”

T

reats as a single site ( requires good connectivity )No Call Admission Control

Will always bypass to trunks enabled for bypass

Network Configuration Setting

Leverages

Region/Sites definition

Each site/Region is assigned Bypass ID

Uses current client location

Client IP address

 Bypass ID

Gateway address (for media)  Bypass ID

Comparison

of the IDs, bypass if the two IDs match

Lync 2010: Media Bypass

How it works – two approachesSlide27

Lync 2010: Media Bypass

How it works – two approachesSlide28

Inbound calls

Mediation receives SIP invite; IP address of media gateway in SDP

Mediation

passes gateway Bypass ID to clients

Client makes bypass decision

Outbound calls

Client

passes Bypass

ID

in SIP Invite

Mediation

determines gateway Bypass ID

Mediation Server

compares, call

is bypassed

if matches

Lync 2010: Media Bypass

Inbound and Outbound logicSlide29

Survivable Branch Appliances

qualified, all support bypass

5 partners – Audiocodes

, Dialogic, Ferrari, HP, NET

Gateways (not all support bypass – see

OIP page

)

Cisco ISR series 28xx, 29xx, 38xx, and 39xx

Avaya 23xx and 41xx

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

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

Centralized IP-PBX with multiple sites

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

Media bypass in multiple sites?? How to --

Define regions and sites in network Configuration

Define (virtual) media gateways in topology builder

Associate media IP in site to each “media gateway”

Define listening ports as appropriate

Establish appropriate routing on both systems

IP-PBX unaware of

Lync

dynamic location;

suggest routing to local trunk

Media Bypass – Multiple Sites, Centralized Signaling

What’s differentSlide31

Media Bypass – Multiple Sites, Centralized Signaling

What’s differentSlide32

Media Bypass with

CUCM

In-branch call between Lync

endpoint

and Cisco phone

via

branch MTP

CUCM (MTP)

Lync

Mediation

PSTN

PBX

Endpoint

Lync

Endpoint

Lync

Endpoint

Gateway

WAN

Cisco

phone

ISR (MTP)

G.711

HQ Site

Orlando BranchSlide33

Media Bypass with

CUCM

In-branch call between Lync

endpoint

and Cisco phone

via

branch MTP

CUCM (MTP)

Lync

Mediation

PSTN

PBX

Endpoint

Lync

Endpoint

Lync

Endpoint

Gateway

WAN

Cisco

phone

ISR (MTP)

G.711

Call stays up

HQ Site

Orlando BranchSlide34

No Media Bypass for Calls on WAN

WAN

call between

Lync

in branch and Cisco phone via central MTP

CUCM (MTP)

Lync

PSTN

PBX

Endpoint

Lync

client

Lync

client

Gateway

Cisco

phone

ISR (MTP)

WAN

G.711

Mediation

RT Audio

Narrowband

HQ Site

Orlando BranchSlide35

Media Bypass with IP-PBX

Branch call with local resiliency

CUCM (MTP)

Lync

Mediation

PSTN

PBX

Endpoint

Lync

Endpoint

Lync

Endpoint

Gateway

WAN

PBX

Endpoint

ISR (MTP)

G.711

Lync SBA

HQ Site

Orlando BranchSlide36

A migration and coexistence plan with CUCM and ISR

Planning Cheat Sheet

Define Topology with CUCM and ISRUse ISR as gateway by CUCM and LyncUse it for PSTN calls by both “PBX”Configure ISR for Media BypassDirect SIP between CUCM and LyncConfigure it for extension calls

by both “PBX”

Including media bypass to CUCM

Migrate

users

stepwise

CUCM (MTP)

ISR (MTP)

Lync

Virtually no additional Hardware requiredSlide37

A migration and coexistence plan with CUCM and ISRSlide38

Takeaway

Integrating natively with IP-PBXs can

Allow low cost Proof of ConceptConnect migrated & non-migrated usersAllow for long term coexistenceNative integration with media bypass enablesCPE-less deploymentKeeping much more of the media local, including in centralized multisite topologies

It is possible!!Slide39

Agenda

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide40

High quality video in every desktop

Improve the

meeting room

experience

Lync

Video

Strategy

High 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

InteroperabilitySlide41

Optimized for Microsoft

Lync

Logo Program

Webcams

PCs

IP devices

Video Partner Programs

NATIVE

SOLUTIONS

INTEROPERABLE SOLUTIONS

New! Video Interoperability

Program

Enable 3

rd

party VTC systems to

interop

with

LyncSlide42

Video Interoperability

Program

Connect with

Lync

2010/OCS 2007 R2

Direct registration

to

Lync

Gateways

to bridge other systems to

Lync

Process

Qualification program

Qualified partner listed on Microsoft website

Requirements

OCS 2007 R2:

Enhanced security, point-to-point

video,

firewall traversal

Lync

2010:

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

Lync MCUSlide43

Partner Approaches

VTC Direct Registration

Register directly

Multiparty

calls on

Lync

AVMCU

VTC

endpoints appear as

contacts

Users can take advantage of existing

Lync

functionality

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

Committed partners

:

Polycom

,

Lifesize

Gateway/MCU

Gateway

pass-through

Multiparty

calls hosted

on partner MCUVirtual rooms appear as

contactsLegacy VCS/telepresence interoperability, multiple views, transcoding

Committed partners:

Polycom,

Lifesize,

RadvisionSlide44

Cisco

Telepresence

Interoperability

No qualified solution available

OCS

2007 R2: in process

Lync

:

ask Cisco/Tandberg

One Possible Solution

VCS

gateway

for signaling

Tandberg “Advanced

Media

Gateway”

for

media transcoding

Need

both to get HD video

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

Recommended approach: Use qualified partner gatewayPolycom

, RadvisionSlide45

Recap

Review Lync 2010 TopologyPlanning for Lync 2010 featuresReference Architecture, High Availability and

ResiliencyInteroperability PrinciplesIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide46

Track Resources

Lync

Team

Blog

:

http://blogs.technet.com/b/uc

/

Lync Facebook

:

http

://

www.facebook.com/MicrosoftOfficeCommunicator

Lync Website:

http://

lync.microsoft.com/en-us/Pages/unified-communications.aspx

Lync Server Blog

:

http://blogs.technet.com/b/nexthop

/Slide47

Resources

Connect. Share. Discuss.

http://northamerica.msteched.com

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn Slide48

Complete an evaluation on CommNet and enter to win!Slide49

Please Complete an Evaluation

Your feedback is important!

Multiple

ways to

E

valuate

S

essions

Be eligible

to win great daily prizes and the grand prize of a $5,000 Travel Voucher!

Scan the Tag

to evaluate this

session now

on

myTechEd

MobileSlide50

©

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