unify² power route for microsoft lync 2010 product overview

© 2010 UnifySquare. All rights reserved. © 210 UnifySquare. All rights reserved. © 2010 UnifySquare. All rights reserved.

Strategy Architecture Solutions

An Overview on how PowerRoute can

be leveraged to enable Lync 2010 to

comply with Telecom Regulations

PowerRoute 1.0

Product Overview

© 2010 UnifySquare. All rights reserved. © 210 UnifySquare. All rights reserved.

The Problem and the Solution

PowerRoute’s Rule-Based Approach and Solution Advantages

PowerRoute Architecture and Management

Sample Topology for a Pilot/Proof of Concept Environment

Sample PowerRoute Scenarios/Rules

Outbound call from a roaming user to the PSTN

Inbound PSTN call to a roaming User

Inbound PSTN call forwarded to a user at a different site in India

Inbound PSTN call forwarded to a number of users

Ad-hoc conferencing (2 scenarios)

PowerRoute Timeline

Engagement Model

Achieving Certification

Q&A

2

Agenda: PowerRoute Introduction


• Telecom restrictions in many countries require national or international long distance calls to go over PSTN – Preserve national and international tolls

– National Security/Legal Intercept

• Regulations exist in over 50 countries, including India, China, Brazil, Algeria, Bahrain, UAE, etc.

• Lync Enterprise Voice and Conferencing deployments are stalled or limited as Lync cannot meet regulations in specific locations

• Major issue in countries such as India

• Critical issue for ANY Enterprise with offices in these countries

The Problem: Lync cannot be configured to comply

with certain National Telecom Regulations

3


• PowerRoute enables telecom compliance by:

– Forcing select calls to be routed over the PSTN in a compliant manner

– Block calls that are non compliant (or may not have sufficient information to determine if it’s compliant)

– Applies call routing rules on a per-country basis, leveraging the user location information in Lync Server 2010.

The Solution: PowerRoute

4

© 2010 UnifySquare. All rights reserved.

Facilitates Lync Server 2010 deployments in India in

achieving certification with national telecom regulation

authorities and service providers.

Reduces administration costs with a single

communications system that IT staff can easily configure

and manage.

Increases employee efficiency by taking advantage of

powerful and easy-to-use Microsoft Lync 2010 clients and

IP Phones for all communications.

Reduce Administration Costs

Drive Lync Deployments

Lowers telecom investment with the deployment of a

single communications solution worldwide, avoiding the

traditional physical partition system compliance solutions.

Increase Employee Efficiency

Lowers

Telecom

Investments

PowerRoute Solution Advantages


• Consists of a set of rules that Allow, Allow with routing restrictions, or Block the call or conference call escalation

• Rules apply to both inbound and outbound calls as the call signaling (SIP INVITE) is processed by Lync’s Front-End Servers

• Rules apply to all forked call legs for inbound calls – Forked calls to each user device, delegate, team call, call forwarding

setting, etc.

PowerRoute: Rules-Based Solution

6


• Rules apply to different classification of users or called/calling parties

– Enterprise UC Users (EntUC) includes any enterprise user using any Lync client/device

– PBX Users on a legacy PBX that may or may not be part of the “Closed User Group”

– PSTN Parties (or SIP Trunk parties) connected through Mediation Servers and Gateways (GW)

• Rules apply to different call types and destination combinations

– Basic 2 party (P2P) calls, Call Forward, Call Transfer, Ad-Hoc Conferencing

– Inbound PSTN call, outbound PSTN call, UC-UC

– Local, national, and international calls

• PowerRoute leverages the actual location of each user and their base location

– User at Base office location,

– User roaming internally (at another office)

– External User (at home, in a hotel)

– Unknown Location

PowerRoute: Rules-Based Solution

7


• Rule-based system that's integrated into Lync Server 2010's core Inbound/Outbound Routing Infrastructure

• PowerRoute runs on Lync 2010’s Front End Servers

• Intercepts SIP messages, and either allowing them, blocking them or modifying them

• PowerRoute works with Lync’s Outbound Routing to force the calls to use specific GWs

• PowerRoute works with Lync’s Inbound Routing, determining which call legs are allowed and which calls should be blocked

• For PowerRoute 1.0, Unify2 has supplied a pre-defined set of rules that are intended to be tweaked to meet the compliant requirements of India Service Providers (SPs) based on Telecom Regulatory Authority of India (TRAI) requirements

• Enterprise achieves compliance by the combination of Lync and PowerRoute configurations based on the enterprise’s topology

PowerRoute: Rule-Based System

8


Lync Front-End Server #2

PowerRoute 1.0 Architecture

PowerRoute

Registrar

PowerRoute Application Infrastructure

PowerRoute

Inbound

Routing

Lync Front-End Server #1

Lync Front-End Server Infrastructure

Lync

Outbound

Routing

Lync

Inbound

Routing

Lync Back-End Database Server PowerRoute

Database Lync

Database(s)

PowerRoute

OutBound

Routing

• PowerRoute runs on Lync’s Front-End and Back-End Servers

– No extra hardware

– Uses Published and Supported Interfaces

• Leverages Lync’s Environment for:

– High Availability

– Resiliency

– Scalability

– Management


Integrated Management with

Lync 2010 Control Panel

10

• PowerRoute is started, stopped and restarted automatically by Lync

• Can be controlled with other Server Applications s via Lync Control Panel


• Sample topology that is used to demonstrate PowerRoute

• Leverage sample configurations for Pilot and Production deployments

• Consists of 3 sites in India (Site Restricted) and 1 site in a country with no restrictions

• 1 Pool:

• AsiaPac

• “Site Restriction” Country

• India (IND)

• Bangalore (BLR) +91 80

• Delhi (DEL) +91 11

• Hyderabad (HYD) +91 40

• “No Restriction” Country

• Singapore (SIN)

• Singapore (SIN) +65

Sample PowerRoute Topology

11


• Enterprise-Voice enabled users are assigned a Voice Policy in Lync that defines:

– A Class of Service (COS)/ set of calling privileges

– How calls going to the PSTN/SIP Trunk are routed

• Here are Sample Voice Policies (and the associated set of “PSTN Usages” for two classes of BLR users:

• User’s assigned Voice Policy doesn’t take into account the user’s location

• PowerRoute will replace the Voice Policy (PSTN Usages) for outbound PSTN calls for roaming users

• Typically an Unrestricted Voice Policy is configured in PowerRoute to enable users to roam liberal calling privileges (and avoid cell phone usage)

Voice Policies/PSTN Usage Overview

12

Restricted BLR User Unrestricted BLR User

Local via BLR GW Local via BLR GW

National via BLR GW

International via BLR GW


• In this scenario an India-based user (IND/BLR) who is roaming at another location (IND/DEL) places an outbound call to the PSTN.

• A PowerRoute rule will match this call pattern which then allows the call, but forces the call to use the PSTN Usage (GW routing) based on the user’s ACTUAL location (e.g. DEL).

Basic Outbound Call Scenario

13

EntUC

User BLR1

in DEL

PowerRoute

/Outbound

Routing

PSTN

Called

Party (+91)

Allow;

Set PSTN

Usage to

use DEL GW

3) The call is placed to the PSTN, using the DEL GW (as opposed to the BLR GW what is used with the user is at their base location). The billing number (ANI) & Caller ID (CLID) for the call is set to a DEL number by the GW (typically a local switchboard number)

2) PowerRoute intercepts the call before Outbound Routing. It determines the call can be placed as long as it uses the GW in DEL. PowerRoute sets the PSTN Usage to the usage for the DEL site.

1) User BLR1 is roaming in DEL dials a national PSTN Number (+91)


• In this scenario an India-based user (IND/BLR) who is roaming at another location (IND/DEL) receives an national Inbound call from the PSTN.

• A PowerRoute rule will match this call pattern which then blocks the call since the user is not at their base site (avoids an inter-site national toll bypass).

• The call this is forwarded to voicemail (if configured)

Basic Inbound Call Scenario

14

PSTN

Caller

(+91*)

EntUC IND/BLR1’s

Inbound Routing

and PowerRoute

EntUC

IND/BLR1

in DEL

EntUC

IND/BLR1

Voicemail

X Block 3) PowerRoute matches this call leg against a rule and then blocks it since BLR1 is not at their base location BLR (in DEL)

2) BLR1’s Inbound Routing tries to route the call to BLR1 in DEL

4) BLR1’s Inbound Routing continues, and if no call forks are answered, it forwards the call onto BLR1’s voicemail (if configured)

1) PSTN calls BLR1 who is roaming at another site in India (DEL)


• In this scenario an India-based user forwards their inbound calls to another India-based user.

– User BLR1 has call forwarding set to User DEL1

– Also has voicemail configured if the call is not answered in a timely fashion.

• If the other user is in another location in India, then the call transfer call leg from BLR to DEL bypasses the PSTN Need to block the call.

Call Forwarding Scenario (Block)

15

PSTN

Caller

(+91*)

EntUC IND/BLR1’s

Inbound Routing

and PowerRoute

EntUC

IND/DEL1

in DEL

EntUC

IND/BLR1

Voicemail

X Block 3) PowerRoute matches this call leg against a rule and then blocks it since BLR and DEL are based at different sites in India

2) BLR1’s Inbound Routing tries to forward this call to DEL1


1) PSTN calls BLR1 who has call forwarding set to DEL1 and Voicemail


• In this scenario an India-based user forwards their inbound calls to two India-based users.

– User BLR1 has call forwarding set to users BLR2 and DEL1 (delegates, team call, etc.)

– Also has voicemail configured if the call is not answered in a timely fashion.

• If the other user is in another location in India, then the call transfer call leg from BLR to DEL bypasses the PSTN Need to block the call.

Call Forwarding Scenario (Allow)

16

PSTN

Caller

(+91*)

EntUC IND/BLR1’s

Inbound Routing

and PowerRoute

EntUC

IND/DEL1

in DEL

EntUC

IND/BLR1

Voicemail

Block 3) BLR1’s Inbound Routing also tries to

forward the call to BLR2 (Allow)

2) BLR1’s Inbound Routing tries to forward this call to DEL1 (Blocked)


1) PSTN calls BLR1 who has call forwarding set to DEL1, BLR2 and Voicemail

Allow

EntUC

IND/BLR2

in BLR


• In this scenario two Ent-UC users are in a 2-way call and one of the EntUC users based in India tries to add a 3rd person (initiate an ad-hoc conference call)

• PowerRoute will block this escalation since it can result in a toll bypass situation (PSTN caller is connected to both BLR1 and DEL1)

Conference Call Escalation (Block)

17

EntUC

IND/BLR1

EntUC

IND/DEL1

Invite to

PSTN

(+91)

Block

3) DEL1 is informed that the call is forbidden

2) DEL1 (or BLR1) invites a PSTN number to join a conference call. A PowerRoute Ad-hoc conference rule matches and Blocks the escalation.

4) PowerRoute restores the previous 2 party session and the initial call continues

1) BLR1 and DEL1 are in an existing 2 party call


• In this scenario a PSTN party and an IND-based EntUC user are in a 2-way call and the EntUC user tries to add a 3rd party into the call (EntUC, PSTN, PBX, …)

• PowerRoute will block this escalation since it can result in a toll bypass situation (PSTN caller is connected to both BLR1 and the additional party)

Conference Call Escalation (Block)

18

PSTN

(any)

EntUC

IND/BLR1

DEL1 or

PSTN (any)

Block

3) BLR1 is informed that the call is forbidden

2) BLR1 tries to invite another party (EntUC, PSTN, etc.) to join a conference call. A PowerRoute Ad-hoc conference rule matches and Blocks the escalation.

4) PowerRoute restores the previous 2 party session and the initial call continues

1) PSTN1 and BLR1 are in an existing 2 party call


• For initial deployments Unify2 recommends they be directly involved in the deployment

– Possibly subcontracting through SI or MCS

• Goal is to be in a position where rules can be tweaked in an efficient manner to achieve timely certification through India SPs

– Unify2 can potentially add new rules; Direct engineering support

– Need expertise for initial engagements and certifications

• MS/India, Unify2 and MSIT are already engaged with India SPs on solution

Engagement Model

19


• The combination of Lync, GW and PowerRoute configurations are what is certified

– Up to Enterprise to maintain this certified configuration (e.g. GWs at every site in IND)

– Certification provided in India through SPs following the rules of TRAI

• MS/India and Unify2 will assist in achieving this certification

– However we will not indemnify the solution

– Enterprise responsible for achieving and maintaining certification

Achieving Certification

20


• Deploy Lync in Pilot lab

– with GWs to simulate production environment

– Initial call with Service Provider(s)

• Deploy PowerRoute in Pilot Lab

– Run through validation tests

• Visit by Service Provider to Certify Solution

• Deploy Lync and PowerRoute in production environment

– Rerun validation tests

– Final Service Provider certification (if necessary)

Typical Engagement

21


• Initially through [email protected]

– Engineers in Singapore and Redmond (and possibly UK) specialized in PowerRoute

– 5 days/week

• Working on the specifics of a Support Agreement package

– Looking at a 24x7 Offering to support production customers

• Working with Microsoft (TSS, PSS) to ensure we can handle critical situations in a timely manner

– Document steps to quickly determine if problem is PowerRoute (disable to remove PowerRoute from call path; Re-Enable)

PowerRoute Support

22

mailto:[email protected]


Steve White

Senior Product Manager

Unify2, Inc.

+1.425.865.0718

[email protected]

Sarbjit Gill

Director, Unify2 Asia

Unify2, Inc.

+65.82018031

[email protected]

www.unifysquare.com

24

Contact Information



© 2010 UnifySquare. All rights reserved.

Strategy Architecture Deployment Products

© 2010 Unify Square, Inc. All rights reserved.

Microsoft, Office Communications Server and other product names are or may be registered trademarks and/or trademarks of other companies.

UNIFY SQUARE MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

unify² power route for microsoft lync 2010 product overview

Technology