Module 6a

Designing Voice Infrastructure

Part 1

Designing Lync Server 2010 Jump Start

Day 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

Module 11: Designing
Infrastructure
Resiliency
TWO

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

Lync Server 2010 Voice Capabilities

Office Communications
Server 2007 R2

Office Communications
Server 2007
Accessible from
anywhere
IM and rich Presence
Common voice features
Unified messaging
Audio and video
conferencing
Desktop integration

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 Topology

PIC MSN
XMPP AOL
Yahoo

Perimeter
Network

Remote
Users

Federated
Business

Archiving Server

UC
Endpoints

UC
Pool
Front End Server
(incl. Mediation

Back End
Server

Active Directory
DNS

AV
Conferencing

Edge
Services
Active Directory

SIP Trunking

Direct SIP
Mediation Server

ExUM

PSTN

IP-PBX

Analog Devices

On-Premise or
online

Media GW/SBA

Circuit
Packet

Telephony Interoperability Options

Virtual Private
Network (VPN)

Mediatio
n Server

VPN
Router

VPN
Router

Session
Border
Controller

SIP Trunking

SIP/PSTN Gateways

IP-PBX Endpoints
(IP Phones)

UC Voice
Endpoints

SIP Over TLS/SIP

Over TCP
Lync Server 2010
Mediation Server

IP-PBX
PSTN

Direct SIP

Lync Server 2010

FrontEnd Server

SIP/PSTN Gateway Functionality

Translates signaling
and media
Mediation
Server

PSTN

Terminates SIP
Trunking

SIP/PSTN
Gateways

Acts as
Intermediary
Lync Server
2010

Connects
Unsupported
IP-PBX

Analog Devices

Lync Server 2010

Infrastructure

Upstream and Downstream Gateway Options

Upstream Deployment
Lync Server 2010
Deployment
PSTN
SIP/PSTN
Gateway

IP-PBX

IP-PBX Endpoints
(IP Phones)

Downstream Deployment
Lync Server 2010
Deployment
PSTN
SIP/PSTN
Gateway
IP-PBX

IP-PBX Endpoints
(IP Phones)

Direct SIP
IP-PBX Endpoints (IP Phones)

UC Voice
Endpoints

SIP Over TLS/SIP Over TCP

Lync Server 2010
Mediation Server
IP-PBX

PSTN

Lync Server 2010

FrontEnd Server

SIP Trunking
External Firewall

Enterprise Network
Internal
Enterprise
User
Front End
Server

Mediation
Server

Service Provider Network

Virtual
Private
Network

VPN
Router

Session
Border
Controller
VPN
Router

PSTN

Softswitch
or IPPSTN GW

SIP Trunk
Internal Implementation
PSTN Trunk

UC Open Interoperability Program

PSTN
Microsoft Lync
Server 2010

SIP/PSTN Gateway
IP-PBX/SIP Trunking
Service

Choosing an Interoperability Option Guidelines

Is there a need to reuse existing
telephone numbers / extensions
/ DID numbers?
Does the site contain PSTN
connectivity with sufficient
capacity?

Is there a requirement for

interoperability with an IP-PBX?

PSTN
Interoperability
Option
Does the PSTN connectivity
require high availability and
resiliency?

What features are required in

relation to PSTN at the site?

Introduction to Dial Plans

Dial Plan

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
Types of
Dial Plans
User Dial Plan

Pool Dial Plan

Site Dial Plan

Global Dial Plan

Gathering Information on Users Dialing Habits

Interviewing telephony
administrators

Interviewing users
Gathering
Information on a
Users Dialing
Habits

Retrieving the current dialing

pattern configuration from an
existing IP-PBX
Determining how different types
of calls are placed

Outbound Dial Strings Formatting

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:
Create rules that can assist in manipulating the Request URI prior to
routing it to the gateway

Format the numbers sent from Lync Server 2010 for different
models of gateways, PBX equipment, and SIP trunks
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
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

Designing a Dial Plan for a Scenario

Local
Extensions

National Calls

Lync Server 2010

Deployment

International Calls

Site Dial Plan

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.