Module 6aDesigning Voice Infrastructure

Part 1

Designing Lync Server 2010 Jump StartDay 1:

Topology Design

Day 2: Infrastructure &

Network Design

Day 3: Services &

Maintenance Design

Mod 1: Lync Server 2010

Design Process Overview

Module 5: Designing a

Mediation Server Topology

Module 9: Designing

Location Services in Lync

Server 2010

Module 2a: Designing a LS

2010 TopologyONE

Module 6a: Designing Voice

Infrastructure

ONE

Module 10: Designing

Response Group Services

Module 2b: Designing a LS

2010 TopologyTWO

Module 6b: Designing Voice

Infrastructure

TWO

Module 11: Designing

Resiliency

Module 3a: Designing for

Conferencing and Ext.

ScenariosONE

Module 7: Designing

Exchange Server UM

Integration

Module 12: Designing for

Backup and Disaster

Recovery

Module 3b: Designing for

Conferencing and Ext.

ScenariosTWO

Module 8a: Creating a

Network DesignONE

Module 13: Designing

Monitoring and Archiving

Server

Module 4: Planning and

Designing Load Balancing

Connectivity

Module 8b: Creating a

Network DesignTWO

Module 14:Planning a

Migration to Lync Server

2010

Module Agenda

Understanding Voice Topology Options

Understanding Gateway Options

Interoperability

Introduction to Designing Dial Plans

Accessible from anywhere

IM and rich Presence

Common voice features

Unified messaging

Audio and video conferencing

Desktop integration

Office Communications

Server 2007

Office Communications

Server 2007 R2

Single number reach

Attendant Console

Delegation/TeamCall

Response Groups

Session Initiation Protocol (SIP) Trunking

Dial-in audio conferencing

Higher definition video UC workflow activities

Lync Server 2010

Branch resiliency

Datacenter resiliency

Call Admission Control

Call park and Unassigned number

Topology changes

Media bypass

Enhanced 9-1-1 (E9-1-1)

Routing changes

Analog devices

Common area phones

Private line

Malicious Call Trace (MCT)

Larger device portfolio

Lync Server 2010 Voice Capabilities

UC

Endpoints

UC

Pool

Front End Server

(incl. Mediation

Back End

Server

Mediation Server

Direct SIPSIP Trunking

Media GW/SBA

IP-PBX

Perimeter

Network

Edge

ServicesActive Directory

Archiving Server

Active Directory

DNS

ExUM

On-Premise or

online

PIC

XMPP

MSN

AOL

Yahoo

Remote

Users

Federated

Business

PSTN

Circuit

Packet

AV

Conferencing

Analog Devices

Lync Server 2010 Voice Topology

SIP/PSTN Gateways

Mediatio

n Server

VPN

RouterSession

Border

Controller

VPN

Router

SIP Trunking

PSTN

IP-PBX

Lync Server 2010

Mediation Server

Lync Server 2010

FrontEnd Server

UC Voice

Endpoints

IP-PBX Endpoints

(IP Phones)

SIP Over TLS/SIP

Over TCP

Direct SIP

Virtual Private

Network (VPN)

Telephony Interoperability Options

Lync Server 2010

InfrastructureLync Server

2010

SIP/PSTN

Gateways

Terminates SIP

Trunking

PSTN

Translates signaling

and media

Mediation

Server

Connects

Analog DevicesUnsupported

IP-PBX

Acts as

Intermediary

SIP/PSTN Gateway Functionality

Upstream Deployment

Downstream Deployment

PSTN

IP-PBX

SIP/PSTN

GatewayIP-PBX Endpoints

(IP Phones)

Lync Server 2010

Deployment

PSTN

IP-PBX

SIP/PSTN

Gateway

IP-PBX Endpoints

(IP Phones)

Lync Server 2010

Deployment

Upstream and Downstream Gateway Options

Lync Server 2010

FrontEnd Server

PSTN

IP-PBX

Lync Server 2010

Mediation Server

UC Voice

Endpoints

IP-PBX Endpoints (IP Phones)

SIP Over TLS/SIP Over TCP

Direct SIP

SIP Trunking

Internal Implementation

SIP Trunk

PSTN Trunk

PSTN

External Firewall

VPN

Router

Internal

Enterprise

User

Front End

Server

Mediation

Server

Softswitch

or IP-

PSTN GW

Session

Border

Controller

VPN

Router

Service Provider NetworkEnterprise Network

Virtual

Private

Network

UC Open Interoperability Program

Microsoft Lync

Server 2010

SIP/PSTN Gateway

IP-PBX/SIP Trunking

Service

PSTN

PSTN

Interoperability

Option

Does the site contain PSTN

connectivity with sufficient

capacity?

Is there a need to reuse existing

telephone numbers / extensions

/ DID numbers?

Is there a requirement for

interoperability with an IP-PBX?

What features are required in

relation to PSTN at the site?

Does the PSTN connectivity

require high availability and

resiliency?

Choosing an Interoperability Option Guidelines

Refers to a named set of normalization rules

Translates phone numbers for a named location, individual user, or contact object into a standard format E.164

Dial Plan

User Dial Plan

Pool Dial Plan

Site Dial Plan Global Dial Plan

Types of

Dial Plans

Introduction to Dial Plans

Gathering

Information on a

Users Dialing Habits

Interviewing telephony

administrators

Interviewing users

Determining how different types

of calls are placed

Retrieving the current dialing

pattern configuration from an

existing IP-PBX

Gathering Information on Users Dialing Habits

Create rules that can assist in manipulating the Request URI prior to routing it to the gateway

Refer the vendor or service provider documentations to understand the formatting of numbers

Resort to diagnostic logging of the SIP traffic between Lync Server

2010 and the affected next hop, if such documentation is not

available

Format the numbers sent from Lync Server 2010 for different models of gateways, PBX equipment, and SIP trunks

Log on to the gateway to determine what is being sent between the

two systems, if you are configuring a SIP/PSTN gateway to interface

with a PBX

To ensure numbers from Lync Server 2010 to the PSTN-connected equipment

are in the required format prior to Routing to PBX/PSTN, perform these tasks:

Outbound Dial Strings Formatting

Designing a Dial Plan for a Scenario

Site Dial Plan

Local

Extensions

National Calls

International Calls

Lync Server 2010

Deployment

2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Azure, System Center, Hyper-V 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.