/
Planning Voice Deployments Planning Voice Deployments

Planning Voice Deployments - PowerPoint Presentation

tawny-fly
tawny-fly . @tawny-fly
Follow
456 views
Uploaded On 2016-03-18

Planning Voice Deployments - PPT Presentation

Mahendra Sekaran Principal Group Program Manager Microsoft Corporation EXL410 Agenda Review Lync 2010 Topology Network Planning Considerations Lync 2010 Interop features IPPBX Interop Media Bypass ID: 261320

pbx lync bypass media lync pbx media bypass interop 2010 branch gateway network site mtp mediation pstn sip endpoint

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
Slide2

Planning Voice Deployments

Mahendra SekaranPrincipal Group Program ManagerMicrosoft Corporation

EXL410Slide3

Agenda

Review Lync 2010 TopologyNetwork Planning ConsiderationsLync 2010 Interop features

IP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide4

Takeaways

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

PBXSlide5

Agenda

Review Lync 2010 TopologyNetwork Planning ConsiderationsLync 2010 Interop features

IP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide6

UM

SCOM

Standard Edition

Enterprise Edition

Topologies

Director

Archiving

Monitoring

Mediation

Group Chat

Optional Servers

Front end

Back end

AV Conf

Edge

Servers

Topologies SimplifiedSlide7

Deployment Model

Global Deployment is a collection of Sites

Sites are made of PoolsPools host users & services (such as IM/P, conferencing, VoIP, etc.Slide8

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/serverSlide9

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/serverSlide10

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 CSlide11

Agenda

Review Lync 2010 TopologyNetwork Planning Considerations

Lync 2010 Interop featuresIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide12

Media

Modality

Codec

Typical BW

Max w/o

FEC

Max w/FEC

Audio

Peer to Peer

RTA-W

39.8

62

91

Audio

Peer to Peer

RTA-N

29.3

44.8

56.6

Audio

PSTN

RTA-N

30.9

44.8

56.6

AudioPSTN

G.71164.897

161AudioConferencing

G.722

46.1100.6

164.6

AudioConferencing

Siren25.5

52.668.6Video

Peer to Peer

RTV - CIF

220260

Video

Peer to Peer

RTV - VGA508

610

Video

Peer to Peer

RTV - HD1210

1510

VideoPeer to Peer

RTV - Pano

269

360

Video

ConferencingRTV - CIF

220260

Video

Conferencing

RTV - VGA508

610

Video

Conferencing

RTV - Pano

269360

Bandwidth - Planning

One-way traffic including media, typical activity, RTCP.

For planning in a well managed, right-sized network, use Max BW w/o FEC.

If the network will be constrained and you want to preserve quality, use Max BW with FEC.When understanding how much bandwidth at any given time is being used, use the Typical BW numbers. Not for planning, as usage will be greater at times.Slide13

Network Planning Considerations

Lync media endpoints adapts to varying network conditionsPlan, Assess, Configure, MonitorUse the bandwidth calculator tools to estimate Lync traffic

Assess your network infrastructure Configure QoS to prioritize A/V traffic; e2e latency < 150ms Continually monitor your network for configuration driftsFor constrained links – configure CAC, disable videoIf IPSec is deployed, recommend disabling IPSec over the port ranges used for A/V trafficSlide14

Agenda

Review Lync 2010 TopologyNetwork Planning Considerations

Lync 2010 Interop featuresIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide15

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 Slide16

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 deviceSlide17

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 deployedSlide18

Agenda

Review Lync 2010 TopologyNetwork Planning Considerations

Lync 2010 Interop featuresIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide19

Lync

Telephony Deployment

“We’re sold – our goal is Enterprise Wide UC as soon as practical”“We love Lync

, but I can’t replace everything yet….”

Lync

is our presence platform, but all telephony will remain on the PBX”

Replace the PBX

Connect with the PBX

Retain the PBXSlide20

Lync

Telephony Deployment

SIP Trunking

Replace the PBX

Direct SIP to IP-PBX

Gateway to TDM PBX

Gateway to PSTN

C

onnect with the PBX

Retain the PBX

More

Costly with Suboptimal UEX

Using

Lync

Voice where practical for the business

Lync

Everywhere

What

How

I

mplications

Separate Servers & Vendors for UCSlide21

Replace the PBX

PBX becomes obviated

Intra-company calls route through PSTN

Sensible for right combination of internal politics,

Δ

over time.

DIDs & Numbering

Move the numbers: Lots of carrier hassle

Get new numbers: Expensive at scale

SIP Trunking

Fastest way to future proof solution

Regional availability

may be an issue

Gateway

Are scale & quantity of Mediation is a concern with SIP Trunking.

Consider deploying behind

PBX’s Gateway

SIP Trunking

Gateway to PSTNSlide22

Connect with the PBX

Who moves?

Locations: Main site first, may make numbering easier.

Job functions: Those that can best prove out the ROI

Depreciation: Old equipment / stations go first, new ones later.

PBX stays resident

GW CapEx on may be disadvantageous if traffic peaks then falls

Does it make sense to reconfigure or replace the shop floor? Emergency campus phones? Garage phones?

Direct SIP

Available for most older IP-PBX

releases  

Blocking interop to aid in compete against

Lync

.

Direct SIP to IP-PBX

Gateway to TDM PBX Slide23

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)Slide24

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-PBXSlide25

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 BypassSlide26

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 bypassSlide27

“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 approachesSlide28

Lync 2010: Media Bypass

How it works – two approachesSlide29

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 logicSlide30

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.xAvaya CS1k 5.x, Avaya CS1k 6.x Alcatel Lucent 9.x, Siemens

3.1RxMitel, Genband, Aastra, and Huawei

Testing and Qualification for

Lync

Interop

Open Interoperability Program – tested or in process of testingSlide31

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 differentSlide32

Media Bypass – Multiple Sites, Centralized Signaling

What’s differentSlide33

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 BranchSlide34

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 BranchSlide35

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 BranchSlide36

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 BranchSlide37

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)

LyncSlide38

A migration and coexistence plan with CUCM and ISRSlide39

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 topologiesSlide40

Agenda

Review Lync 2010 TopologyNetwork Planning Considerations

Lync 2010 Interop featuresIP-PBX InteropMedia BypassMigration ApproachesVideo InteropSlide41

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

InteroperabilitySlide42

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 contacts

Legacy VCS/telepresence interoperability, multiple views, transcodingCommitted partners:Polycom

, Lifesize,

RadvisionSlide43

Recap and Takeaways

Lync 2010 supports a variety of topologies, pick the most appropriate topology for your business needsAlthough Lync 2010 endpoints adapt to varying network conditions, it is important to plan, assess, and continually monitor your network

infrastructrureLeverage the new Lync 2010 routing features to simplify your interop configurationLync 2010 offers a lot of flexibility in IP-PBX interop topologies - leverage media bypass to reduce TCO

Lync 2010 offers interoperates with all leading video systems natively or through a video

interop

gatewaySlide44

t

hank you …Slide45

Resources

Connect. Share. Discuss.

http

://europe.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 Slide46

Evaluations

http://europe.msteched.com/sessions

Submit your evals online Slide47

©

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.