migrating to unified communications with microsoft lync - moving off the pbx

2011 AudioCodes Ltd.

All rights reserved.

AudioCodes Confidential Proprietary

Copyright 2012 AudioCodes, Ltd. All rights reserved. No duplication or re-broadcast without explicit permission.

Migrating to Unified Communications

with Microsoft Lync

Session #3 Moving off the PBX?

If, why, when and how.

April 2012

The audio portion of todays program is available via your PC speakers/headphones or by dialing: +1-719-457-6443, passcode: 679799


Housekeeping.

To reduce interrupts and noise, all lines will remain on mute

To pose a question/comment, please use the Q/A menu

A link to the recording of todays presentation and the slide deck will be sent in a few days via email.

Want early access to the slides? Follow @AudioCodes on Twitter or LinkedIn

The audio portion of todays program is available via your PC speakers/headphones or by dialing: +1-719-457-6443, passcode: 679799


Great Drawings! Nine opportunities to win!

To enter the drawing, you must complete the survey to be presented at the end of todays session (on-demand viewers too!)

Drawing for Vacation Voucher will occur after the last session and be based on all survey responses collected during the webinar series

Up to eight chances per person to with the Vacation Voucher

Drawing for iPad 2 will be from survey responses for the month & held at the end of each month

One chance per person per month for the iPad drawing

Winners will be notified via email

Only US Legal Residents are eligible

Complete drawing rules can be found at: http://www.audiocodes.com/uc-migration-series

8 x

$2,000 Vacation Voucher!


UC Migration with Microsoft Lync Series

Branch Office Deployments and Survivability

Call Recording and Compliance with UC

Unified Messaging - Integrating the Desktop

Implementing IM/Presence/Voice & Video

Emergency Services and E911 with UC

Moving off the PBX

SIP Trunking Turning on the Cost Savings

UC Mobility - Taking it on the Road


Todays Presenters

Alan D. Percy

Sr. Director, Marketing NA

Franois van Hemert

Architect

Voice Center of Excellence Matt McGillen

Solution Architect


Todays Agenda

Whats Next?

Survey / Feedback

Q/A

Introductions and Housekeeping

Session Overview and Goals

Best Practices - Microsoft

A Customer Experience - Proficient

Migration tools from AudioCodes

Moving of the PBX / IP-PBX Enabling Lync for Enterprise Voice

Franois van Hemert, UC Voice Architect [email protected]

Session objectives

Enabling Lync Enterprise Voice

How to connect Lync to the PSTN and existing PBX

Common scenarios and recommended architecture

Understand the challenges and discuss possible solution

High level overview of configuration

Lessons learned

Franois van Hemert About me

Veldhoven, The Netherlands

Working in ICT since 1987

Working on LCS/OCS/Lync since 2007

Microsoft Consultancy Services (MCS) since 2008

Part of the Voice Centre of Excellence 24 Voice architects world wide

Supporting MCS and partners on Lync Voice

What does moving of the PBX mean?

Enabling the end-user for Unified Communications One integrated communications experience

Telephony as one of the modalities Offered from the Lync 2010 Infrastructure

Offering well known telephony features

Integrated with conferencing, presence and other modalities

No longer a silo or island

Part of a richer experience

Centrally managed

Starting Point How (almost) all Lync Voice projects start

Things to consider & discuss

The numbering plan Keep the existing or add new?

The Dialing habits Copy the existing or .?

Class of Service Duplicate or reconsider?

Other telephony features (call park, hunt groups, )

Existing PBX

PSTN

Existing Phone Handsets

Numbering Plan

+31-20-500 1000 to

+31-20-500 1999

4 digit Internal extensions

9 for an outside line

3 digits + extension for other locations

.. Dialing Habits

No premium

Local, National

International

No premium

Local, National

Class of Service

Question: How to connect Lync to the PSTN ?

The first important choice to make Most common scenarios

Connect through the PBX

Why? What we always do

PBX owns number plan

User can keep own number

Internal calling at no cost

Benefit from the existing PBX infrastructure

Benefit from existing trunk capacity

Why not? PBX Dependencies

Additional PBX cost

Requires PBX configuration

What happens when migration is done?

Migrating a user = changes in the PBX

or Directly to the PSTN

Why? Easy and fast

No additional PBX investments and configuration

Why not? New numbers for the end-user

Need additional trunk capacity

Migrating a user = changes at the Provider

PSTN

Existing

PBX

Lync 2010

PSTN

Lync 2010 Existing

PBX

Or even a third scenario? Where advanced gateways show true value

If you want to: Avoid depending on the legacy PBX

Maintain number portability

Avoid additional investments in PBX licenses, hard- and software

Facilitate easy user migration between platforms

Consider: Introducing an intermediate connection layer and

Active directory integration

Active Directory

Domain Controller

PSTN

Existing PBX

Lync 2010

Lync Qualified Gateway

How does it work?

Active Directory

Domain Controller

PSTN

Existing PBX Lync 2010


Routing decisions are dynamic

Routing is based on LDAP answers

Default route is to the PBX

To migrate a user Enable the account for Enterprise Voice

The msRTCSIP-Line attribute will be filled

Delete the number from the PBX

Yes No

Default Route

If you Enable a Lync user for Enterprise Voice, number portability is automatic

Lync Enterprise Voice components Connection alternatives

Front End Server

Backend Database

Mediation Server

2. SIP Trunk Directly to the PSTN

SBC Session Border Controller

1. ISDN Connection to the PSTN


3. Direct SIP to Lync Qualified IP PBX

Lync Qualified IP PBX

4. ISDN Connection to legacy PBX

Lync Qualified Gateway Legacy

PSTN

Monitoring Server

Can be co-located on

the Front-End Server

Essential to monitor

Quality of Experience

ISDN IP

IP

IP

IP

ISDN

ISDN ISDN

Connecting Directly to the PSTN

PSTN

IP / SIP

1. ISDN Connection to the PSTN

Traditional connection

Location bound, limited scalability and fault resilience

A gateway is required for IP to ISDN conversion

PSTN

IP / SIP

2. SIP Trunk Directly to the PSTN

Scalable and flexible

Connect over the internet or using a SBC (Session Border Controller)

Lync Server

Lync Server

ISDN

Lync

Qualified

Gateway

Lync

Qualified

SBC

Lync

Qualified

SIP Trunking

provide

Connecting through the PBX

PSTN

IP- PBX

Qualified

For Lync

IP / SIP

3. Direct SIP to Lync Qualified IP PBX

The PBX supports IP

The PBX is qualified for Lync (UCOIP)

Connection will be based IP

PSTN

Non-IP

PBX

IP / SIP

ISDN

4. ISDN Connection to legacy PBX

The PBX does not support IP

Connection will be based on ISDN

A gateway is required for IP to ISDN conversion

Lync Server

Lync Server

Lync

Qualified

Gateway

Qualified Devices Unified Communications Open Interoperability Program

Qualification program for enterprise telephony services and infrastructure

Ensures seamless experiences with setup, support, and use

Rigorous and extensive testing by independent third party.

Ensure that vendors provide interoperability in a consistent and supportable manner

http://technet.microsoft.com/en-us/lync/gg131938

Or search for Lync UCOIP

Numbering formats E.164

ITU-T recommendation (coordinates standards for telecommunications)

Defines the format of telephone numbers

Maximum of 15 digits, usually with + prefix

Makes numbers globally unique

Example :020-5002144 +31205002144

National Destination Code

Subscriber Number Country Code

Lync uses E.164 internally

Most PBXs do not! Requires number manipulation

Most Users do not! Requires number normalization

Dialing habits from a user perspective Normalizing numbers to make life easier

Goal is to: Accommodate existing dialing habits

Convert to E.164 as soon as possible

Carefully consider every Habit,

Do not rebuild the PBX because you can!

User dials Remark Replicate in Lync? 2144 Internal dialing YES - translate to +31205002144

248 2144 Trunk access code for inter-company dialing NO - 248 is only PBX related

0205002144 National number YES - translate to +31205002144

90205002144 Access code for external dialing NO 9 is PBX specific

Requires number normalization at the Lync clients Lync 2010 client

Lync 2010 Phone Devices

Dialing habits PBX perspective Because PBXs dont understand E.164

Goal is to: Convert numbers from and to the PBX

Enable internal and external dialing

Convert E.164 numbers to a format the PBX understands

Example Remark Translate to

+31205002144 Internal number, owned by the PBX 2144

+31401234567 National number, need the PBX outside

access code

9 0401234567

+1408555203 International number, need the PBX outside

access code

9 001 408555203

Requires number manipulation at the Lync PSTN Trunk

Class of Service Controlling what people can and cannot do

Goal is to:

Grant or deny telephony features to the end-user

Control outbound destinations

Lync implementation:

Use voice policies to enable features

Use PSTN usages to control outbound calling

Requires Lync Voice Policies assigned to the user

Requires Lync PSTN usages assigned to the routes

The Big picture Normalization, Manipulation and Class of Service

Front End Server

Backend Database

Mediation Server

PSTN

Dial Plans -------------------------------------

Normalization rules:

Internal E164 National E.164 International E.164

Trunk Configuration ------------------------------------

Number manipulation:

E.164 -> Internal E.164 -> National E.164 -> International

Routes -------------------------------------

PSTN usages:

Internal National International Premium

Voice Policies -------------------------------------

Features:

Enable call forwarding Enable call delegation Enable call transfer Enable call park Etc. PSTN Usage:

Allow Internal Allow National

Monitoring Server

Lync Phone Devices

Lync Qualified IP PBX

Lessons learned

Technical requirements are no business requirements It is all about the end user, understand what he wants!

It is all about Unified Communications We are not replacing the PBX

The Open Interoperability Program is important Make sure your devices are on the list

Assess the Network! The most important component of your deployment

Use E.164 number formats Always, even if the PBX does not understand

Deploying Lync monitoring To troubleshoot and proactively monitor call quality

When deploying gateways Work with the gateway vendor for installation and configuration

Resources

Public documentation http://www.microsoft.com/download/en/details.aspx?id=23888

Open Interoperability Program http://technet.microsoft.com/en-us/lync/gg131938.aspx

Phones and Devices Qualified for Microsoft Lync http://technet.microsoft.com/en-us/lync/gg278164.aspx

NextHop: Microsoft Lync Server Documentation Hub http://blogs.technet.com/b/nexthop/

Lync.com http://lync.com

Thank You [email protected]

Terms

PBX Private Branch Exchange that serves a particular business or office

PSTN Public Switched Telephony Network

SIP Trunk Connection to a SIP Trunking provider

ISDN Integrated Services Digital Network Communications standard for transmission over the traditional circuits of the public

switched telephone network.

Direct SIP SIP Connection to a qualified PBX

Enterprise Voice Delivering voice from Lync to enhance or replace the PBX

Qualified for Lync 2010 Devices & services listed on the UCOIP (Unified Communications Open

Interoperability Program) page

Lync Mediation server Translates signaling and, in some configurations, media when connecting to a PBX,

the PSTN or a SBC

Lync 2010 + AudioCodes

Integrating with Existing Phone Systems Matt McGillen - Perficient

Introduction

National Systems Integrator 15 offices and 2,000 employees

Microsoft Gold UC Voice and Messaging

Many Dozens of Lync / OCS PBX integrations

2 Microsoft Lync Master-trained resources on staff

Perficient (formerly PointBridge)

Lync + PBX Case Study

Needed to upgrade Avaya or buy new phone system

ROI Avaya gave them no new features/functions, Lync required new handsets but had many more features

Avaya S8500

Single major site

3rd party Audio Conferencing

3rd party Web conferencing

Already had Lync for IM/Presence

Large Private Advertising Agency

Lync + PBX Case Study

1 AudioCodes Gateway (M1k): SBC / PRI / SBA / Analog

SBC for SIP Trunking (with MPM for transcoding)

PRI during Co-Existence

Analog for 12 Fax Machines (3 FXS modules w/ 4 ports)

SBA for survivability if Lync goes down, phones register to AudioCodes Gateway

New Polycom CX600 / CX500 handsets

No new Lync Licenses

Lync Solution

Co-Existence and Integration

Designing and Architecting Solutions

Adding SIP Trunking


Ultimate Replacement






Migrating to Unified Communications

with Microsoft Lync

Session #3 Moving off the PBX?

If, why, when and how.

April 2012


Some Migration Considerations

Business factors that affect the long-term role of the PBX: Existing contracts and Maintenance costs

Amortization status

New Equipment costs

Survey the PBX usage/applications Examples: ACD and Park/Hold/Pick-up

Take an inventory of the Non-UC devices/end-points Fax machines

Overhead paging

Door entries / Harsh Environments

Emergency phones (parking lot, pool, elevator)

Understanding your users


Planning Your Next Move

Start

PBX

Investment?

Special

Applications?

Integrate Lync to PBX

Use Lync to Replace PBX

High Low

No Yes

Plan long-term for PBX Retirement


IP-PBX or PBX

Lync Phones Trunks

IP

TDM

Fax

Firewall Router

Analog Phones

PSTN

Lync / PBX Integration Architecture

Internet LAN

Outlook and Lync Clients

AudioCodes Media Gateway

LAN

Existing Digital Phones

PBX is retained and UC Enabled


Lync Phones Trunks

IP

TDM

Fax

Firewall Router

Analog Phones

PSTN

PBX Replacement Architecture

Internet LAN

Outlook and Lync Clients

AudioCodes Media Gateway

LAN

AudioCodes FXS

Media Gateway

POTS and analog devices integrate

with Lync via FXS Gateway


Unified Communications Building Blocks from AudioCodes

Features MediaPack 1xx Mediant 800 Mediant 1000 Mediant 2000 Mediant 3000 Mediant 8000 Office Communications Server 2007 R1/R2 (Gateway Type)

Basic Basic

Basic

Basic-Hybrid

Basic

Basic-Hybrid

Basic Basic

Lync Server 2010 (Gateway Type) Filed Upgradable - Firmware upgrade

Analog Device Enhanced

Enhanced

SBA

SPS

Enhanced

SBA

SPS

Enhanced Enhanced

Microsoft Exchange Server 2007 & 2010 (Gateway Type)

IP Gateway IP Gateway IP Gateway IP Gateway IP Gateway IP Gateway

Max PSTN Channels 2/4/8/24 30 120 480 2,016 16,000

PSTN Interfaces

FXS/FXO

Up to 24 FXS or 8 FXO ports

Up to: 1 E1/T1

4 BRI ports 12 FXS/FXO

Mix of: 1 - 4 E1/T1 1-20 BRI

4-24 FXS/FXO

1 -16 E1/T1 trunks Up to

63/84 E1/T1 trunks

Up to 8xOC-3 (STM-1) ports,

Up to 24xT3 (DS-3) ports

Up to 252 E1/T1/J1 trunks

Modularity Fixed configuration

analog gateway

Fixed configuration

gateway Full Modularity

Fixed configuration digital gateway

Fixed configuration digital gateway

Full Modularity

SBC / IP to IP N/A

Full E-SBC Up to 24

concurrent Sessions

Full E-SBC Up to 150 concurrent Sessions

IP to IP Up to 240 concurrent Sessions

Full E-SBC Up to 1000 concurrent Sessions

B2BUA Transcoding Application


AudioCodes 360 Support

Microsoft Unified Communications

Media Gateway

.

Quality

Analysis

Deploy & Installation

Design & Planning

Post Sales Support Project Management

Media Gateway

E1/T1/BRI/FXO/FXS

Fault

Analysis

Optimization Period Support

Enterprise

PSTN

PSTN

Planning Assessment High Level Design Migration Planning Detailed Design Staging plan Implementation Plan

Media GWs Configuration & Deployment

VOIP Deployment and Acceptance

PSTN and PBX telephony integration

Installation Services integration and migration

between current & target voice infrastructures

Planning & Design

Implementation

Targeted for MSFT Channels and VSPs Utilizes the PDI services Framework


Our Next Session

SIP Trunking Turning on the Cost Savings

Partners: May 15, 2012 End-Users: May 17, 2012

Discussing the integration and security challenges

Best practices

Review the various deployment architectures

Discuss valuable migration techniques

Review a customer case study

Presenter: Kam Toor, Senior Program Manager Lead, Microsoft

+ An end-user Case Study


Survey Time!

8 x

$2,000 Vacation Voucher!

We appreciate your feedback!

Please complete the short survey

http://www.surveymonkey.com/s/UCMIGRATION


Q/A and To Learn More:

Questions: Use the Q/A menu on Live Meeting

More on Lync solutions at: www.audiocodes.com/Lync Whitepapers

Recorded webinars

Videos

Datasheets/Brochures

Social Media Twitter @AudioCodes

or @AlanDPercy

LinkedIn

AudioCodes

AudioCodes / Lync Resource Center Group





Thanks!

More on Lync solutions at: www.audiocodes.com/Lync

Alan D. Percy [email protected]

Twitter: @AlanDPercy

migrating to unified communications with microsoft lync - moving off the pbx

Documents