Microsoft Lync & Acme Packet Session Management Solutions April 2012

Geraint Evans, Technical Channel Director, EMEA

gevans@acmepacket.com

This material is designed for Acme Packet & Microsoft Lync solution architects that need to:

Implement Lync SIP trunking with enterprise SBC (E-SBCs)

Leverage Enterprise Session Management (ESM) to successfully deploy Lync enterprise voice in a multi-vendor IP-PBX environment

Agenda:

Deployment challenges

Applications of E-SBCs and Session Managers

Use cases

Acme Packet solutions for Lync SIP trunking & Session Management

Introduction & agenda

SIP Trunking deployment challenges Potential interop problems with SIP trunk provider (i.e.

support of all of the SIP protocols, methods, and variants used by provider)

Security concerns Routing challenges (i.e. routing of incoming calls to the right place)

Session Management deployment challenges

Making calls between Lync and legacy IP-PBX element Implementing dial plans in every Lync & legacy IP-PBX

elements

Lync enterprise voice deployment challenges Legacy IP-PBX vendors fight it as a means of retaining

customer control

Deployment challenges

Functions of Acme Packet E-SBCs

SIP Trunk Services

Remote Workers

SIP Trunk Provider

B2B Services

Strong Security

• Protect IP

network

boundaries

• Privacy

Easy

Interoperability Assured reliability Compliance

• SIP interworking

• Protocol

interworking

• Quality user

experience

• Enables

business

continuity

• Session

replication for

recording

Enterprise

UC Vendor Agnostic

E-SBCs solve real problems for the customer, VAR and Service Provider Faster, easier deployment and time to service

Most medium / large enterprises are embracing the solution

They are rapidly becoming included in most IP telephony & UC vendor reference architectures Avaya, A-LU, SEN & Cisco include SBCs in their enterprise IP

telephony & UC reference architecture Acme Packet SBCs are qualified for use in MSFT OCS/Lync

architectures http://technet.microsoft.com/en-us/ff799212.aspx http://technet.microsoft.com/en-us/lync/gg131938.aspx#tab=5

Many Service Providers are including SBCs to terminate their

SIP Trunks Vendor agnostic solution to accelerate time to service revenue

E-SBCs – Why should you care?

SBCs & 3 flavours of Lync

Local Lync Clients

Lync FE Server

Lync Mediation

Server

Lync Edge

Servers PSTN

SIP Trunk

Enterprise Voice Service Provider

SP Core & Access to PSTN

PSTN

Remote Lync Clients & Federations

Internet

Lync FE Server

Lync Mediation

Server

Lync Edge

Servers

SIP Trunk

Office 365 Cloud Voice Service Provider

SP Core & Access to PSTN

Lync Clients Internet

Lync FE Server

Lync Mediation

Server

Lync Edge

Servers

SIP Trunk

Hosted Lync Operator Voice Service Provider

SP Core & Access to PSTN

Lync Clients Internet

Enterprise Premises

Lync

Office 365

Lync

(MS Hosted -

Part of BPOS)

“SP Hoster Pack” Lync

(Lync hosted by

third-party SP)

Enterprise

Enterprise

Migrating from TDM – PBX Vendor View

Legacy vendors try to fight Lync deployments with their own session management strategy or agendas

“Before” view

• PBX(i.e. Avaya or Cisco) is the “session

manager”

• Gateway (GW) for PSTN trunking

PSTN

Legacy Telephony Vendor

Lync Environment

“After” view

• All Lync calls routed through IP-PBX or Session

Manager elements

• E-SBC used to terminate SIP Trunk

Legacy Telephony Vendor

Lync Environment

PSTN

SIP

SIP TDM

PSTN – Lync

call routing via

IP-PBX & GW

Why keeping legacy vendors in Lync call paths is a bad thing

Keeping legacy voice vendors in call path can:

Introduce additional voice management costs

Impedes full migration to Lync enterprise voice

Complicate call troubleshooting

Limit future Lync calling features due to incompatibilities with IP PBX

Legacy PBX vendors are fighting to keep their voice role

But why should Lync deployments be limited by this?

Shouldn’t enterprises be able to choose the call routing?

Is there a better and UC vendor-neutral solution?

Enterprise Session Management is a function not a product

E-SBC provides security, interop, routing and dial plan management on one platform

ASC provides routing, dial plan management and Web 2.0 integration on dedicated server platform

Introducing Session Management Solutions Optimized for Lync

Enterprise Session Director

Application Session Controller

Net-Net Session Manager Solutions

Integrated model: Use session management on E-SBC All SBC & session management features performed on E-

SBC Security, interop, routing on a single network element

Standalone model: Use standalone session manager

E-SBC for security, interop, and control functions Standalone session manager for dial plan management

Two session management models

E-SBC &

Session

Manager

PSTN

DMZ

PSTN

DMZ

Standalone ESM Models Integrated ESM Model

E-SBC

Customer requirements are not all equal

Some customers want a integrated model

Leverage E-SBC investment for dial plan management and interop functions

May not need some of the advanced capabilities available on Acme Packet’s standalone models

Other customers will prefer a standalone model

Volume of PBXs & complexities of multi-vendor UC environment drives the need for a separate element

Separation of security and routing functions

Why both session management models are needed?

Migrating from TDM – Acme Packet view

Session management helps move to SIP trunking

Lync calls get routed directly via ESM

Simplified dial-plan and call routing

No loss of functionality and improved interworking

Legacy Telephony Vendor

Lync Environment

PSTN

Enterprise Premises

SIP

SIP TDM

PSTN – Lync

call routing via

IP-PBX & GW

TDM Trunking

Legacy Telephony Vendor

Lync Environment

PSTN

Enterprise Premises

SIP

SIP

SIP

PSTN – Lync

call routing

via

E-SBC & SM

SIP Trunking

E-SBC &

Session

Manager

Microsoft Lync & Acme Packet Session Management Solutions Deployment Models

March 2012

Session management deployment models

Multiple deployment models exist:

1. ESM integrated into E-SBC with On-Premises Lync

2. Standalone ESM with On-Premises Lync

3. SM integrated into E-SBC with Office 365-D Lync

4. Standalone SM with Office 365-D Lync

More details in subsequent slides…

Use Case #1: ESM in E-SBC with On-Prem Lync

ESM integrated into E-SBC model

Net-Net ESD performs security, interop, and SM routing functions

SM routing functions = PSTN calls to/from legacy systems & Lync

For calls to PSTN, IP-PBX & Lync dial plans send calls to E-SBC

For calls from PSTN, E-SBC sends calls to legacy IP-PBX or Lync based on called party info

E-SBC can also route calls between IP-PBX & Lync

Lync Media Bypass supports allows for media path efficiencies

Legacy Telephony

PSTN

DMZ

Enterprise

Premises

Site A

Enterprise

Premises

Site B

Other enterprise UC apps

requiring E-SBC support

(i.e. legacy video

conferencing)

E-SBC &

Session

Manager

When Use Case #1 would apply

Use Case #1 applies when:

Customer is using on-premises Lync

Customer is using (or planning to use) an E-SBC for SIP trunking

Customer is OK with performing session routing, security, and any necessary interop fixups in the same E-SBC element

Customer is OK with routing internal sessions (i.e. between Lync and legacy IP-PBX) via the E-SBC element that is typically in the DMZ

If the above conditions are not met, then a standalone ESM model would be more appropriate (Use Case #2)

Use Case #2: Standalone ESM with On-Prem Lync

Standalone SM model

SM functions separated from E-SBC element

E-SBC element performs security and interop functions

SM element performs routing & advanced dial plan management

For calls to PSTN, legacy IP-PBX & Lync dial plans send calls to SM (which routes to E-SBC)

For calls from PSTN, SM receives calls from E-SBC and sends calls to legacy IP-PBX or Lync based on called party info

SM can also route calls between IP-PBX & Lync

Lync Media Bypass supported

Legacy Telephony

PSTN

DMZ

Enterprise

Premises

Site A

Enterprise

Premises

Site B

Other enterprise UC

apps requiring E-SBC

support (i.e. legacy

video conferencing)

E-SBC Session

Manager

When Use Case #2 would apply

Use Case #2 applies when:

Customer is using on-premises Lync

Customer is using (or planning to use) an E-SBC for SIP trunking

Customer wants to perform session routing and any necessary interop fixups in a ESM element separate from the E-SBC

Customer wants to route with internal sessions (i.e. between Lync and legacy IP-PBX) via a standalone ESM element (vs. other methods)

Use Case #3: SM with Office 365-DLync

Office 365 (dedicated) model uses Net-Net ESD with integrated SM and E-SBC functions in a manner similar to On-Premises Lync model

E-SBC used for security & interop and routing

All calls between PSTN, legacy IP-PBX and Lync are routed via E-SBC element

Lync Media Bypass supports allows for media path efficiencies

Legacy Telephony

Office 365 Lync Clients

PSTN

DMZ

Enterprise Premises

Other enterprise UC apps

requiring E-SBC support

(i.e. legacy video

conferencing)

Media bypass/TLS/SRTP

E-SBC &

Session

Manager

Use Case #: Standalone SM with Office 365 (dedicated) Lync

Office 365 (dedicated) model uses a standalone SM in a manner similar to On-Premises Lync model

ESD provides E-SBC functions used for security & interop

SM used for routing

All calls between PSTN, legacy IP-PBX and Lync are routed via E-SBC + SM element

Lync Media Bypass supports allows for media path efficiencies

Legacy Telephony

Office 365 Lync Clients

PSTN

DMZ

Enterprise Premises

Other enterprise UC apps

requiring E-SBC support

(i.e. legacy video

conferencing)

Media bypass/TLS/SRTP

E-SBC

Session

Manager

Acme Packet products for Enterprise Session Management

For ESM integrated on E-SBC model:

Net-Net ESD-4500 appliance (500 – 16K sessions)

Net-Net ESD-3820 appliance (150 – 8K sessions)

Net-Net ESD-Server Edition SW (25 - 250 sessions)

For standalone session management model

Net-Net ESD options listed above

Net-Net ASC software (up to 20K sessions)

These products have been through UC OIP either via SBC or SIP trunking provider category

Acme Packet + Lync details: www.acmepacket.com/lync

Acme Packet product details: www.acmepacket.com

Summary

Acme Packet’s solutions for Lync are

Qualified via Microsoft UC OIP

Successfully deployed in Global 500 enterprise networks

Widely used by ITSP SIP trunk service providers

Acme Packet’s solutions for Lync also provide:

Vendor-neutral session management capabilities

Supports key Lync enterprise voice features including media bypass, TLS/SRTP, DNS LB, etc.

A better means of deploying Lync enterprise voice

Acme Packet: Not just another E-SBC vendor

Enterprise & service provider SBC market leader

Over 1,500 customers worldwide

Majority of UC OIP ITSPs are using Acme Packet

First vendor to be UC OIP qualified as an SBC

Also MS-qualified for Exchange UM & O365-D

Selected as SBC vendor for Lync Hosting Pack

Flexible packaging (appliance or SW-only options)

Acme Packet hardware, third party server, and virtual machine packages

Scales from 25 to 16,000 concurrent sessions

Multiple session management solution options

Thank you