Doug LawtyArchitectMicrosoft Corporation

Location-based routingVOICE303

Session Objective(s): Explain Lync Server 2013 location-based routing capabilities.Recommend solutions using location-based routing to enable regulatory compliance or optimize call paths.Identify limitations in location-based routing implementations.

Location-based routing can addressmany customer requirementsLocation-based routing must beimplemented with care

Session Objectives And Takeaways

Lync voice routing

Voice Routing

Routing: why bother?

Essentially, routing of VoIP calls is making the choice between using WAN resources or using the PSTNIf all PSTN calls were free, we would simply route to the closest PSTN gateway.Cost is the driving factor for routing.

But, LBR let’s us address two other factors:Regulatory complianceOptimized call path for quality

PSTN

WAN

LCR vs. LBRLeast cost routingRoute call to the gateway closest to the called partyMinimize toll charges (toll bypass)Maximize use of WAN

Location-based routingRoute call to the gateway closest to the calling partyMinimize use of WANEnable compliance with regulations that disallow LCR

These are not mutually-exclusive. Use both!

Location-based routing

Location-based routing introductionComply with regulations that restrict IP-to-PSTN routingRoutes PSTN calls to prevent toll bypass based on the location of the callerScoped to specific locations, gateways, and usersDelivered post-RTM of Lync Server 2013

Location-based routing capabilitiesRoute outgoing calls to a PSTN gateway local to the caller’s locationPrevent incoming calls if the Lync client is not in the PSTN gateway’s locationRoute outgoing calls through international PSTN gateways when there is no local gatewayEnsures that conferences do not have a mix of users from different locations and PSTN dial-out

LBR in pictures

PSTN

Site A Site BWAN

PSTN

Site A Site BWAN

GOOD BAD

Stop. Demo time.

Location-based routing

LBR logic

Outbound RoutingStart

Is global LBR on?

No

Normal ProcessingYes Is source site known and LBR

enabled?

Yes

Do not allow callNo

Use Usages in User͛�s Voice policy

Stop

Route only to non-LBR enabled trunks

Use next usage in user͛�s Voice policy to check if call

is authorized

No

Is call authorized by user voice policy? Yes

Are additional usages on the policy?

Yes No

Use usages from Site VoiceRoutingPolicy to

route call

Normal Processing

Is userenabled for LBR? Yes

No

Outbound RoutingYou can see one policy for authorization and a different policy for routing

Trunk-to-trunk routing

Stop

Is source trunk LBR enabled?

Select next applicable usage.

Are source and destination trunks

sites the same?

YesNormal Processing

No

Select next applicable usage.

Is destination trunk LBR enabled?

No

Do not allow callYesNoAre additional usages in the site?

Do not allow call

No

Yes

Use usages from source trunk associated site

Use the usages of the user �͛s voice policy

Yes

Are there additionalusages? NoYes

Use the usages specified in the trunk config

Is request FWD/XFER/Simulring?

No

Yes

Are source and destination trunks

sites the same?

No

Yes

Start

Inbound routingStart

Is Global LBR switch on? Is from Phone? Get site associated

with the trunkYes Yes Is source trunk LBR ? Yes

Is endpoint in the gateway site?

YesRoute to endpoint No Route to UM

Stop

No

No

No

ConferencingLBR conferencing application ensures that a single conference does not contain VoIP users from different sites and PSTN dial-out.

Current meeting participants Allowed Not allowedLync endpoints all in same network site

PSTNLync (same, different, or unknown site)

None

Lync endpoints from different sites Lync (same, different, or unknown site)

PSTN

Lync endpoints in the same site and PSTN

PSTNLync (same site)

Lync (different or unknown sites)

Implementation

LBR RequirementsServersAll servers must be Lync Server 2013 with latest updates.

ClientsA client must report its location in the ms-subnet SIP header. Otherwise considered to be in an unknown region.

Client type Supported Details Lync 2013 yesLync 2010 yes  Office Communicator 2007 R2 no  Lync Phone Edition yes  Lync Attendant yes  Lync for Windows 8 no  

Lync Mobile 2013 noVoIP must be disabled for Lync Mobile 2013 clients if used by users with Location-Based Routing enabled.

Lync Mobile 2010 yes  

Configuring location-based routingUse existing Lync networks sites/subnetsCreate voice routing policies and assign to sitesTrunk configuration identifies if gateway should enforce location restrictionsDo this only for PSTN gateways – not internal PBX routes

Modify voice policies to enable usersEnable location-based routing configuration

Voice routing policyCreate a voice routing policyNew-CsVoiceRoutingPolicy –Identity <PolicyID> -Name <PolicyName> -PstnUsages <Usage1>, <Usage2>User’s assigned voice policy is used for authorizationVoice routing policy assigned to site is used to select gateway

Enabling location-based routingGlobal flagSet-CsRoutingConfiguration -EnableLocationBasedRouting $true

User’s voice policySet-CsVoicePolicy <PolicyName> -PreventPSTNTollBypass $true

Network siteSet-CsNetworkSite -Identity <SiteID> -EnableLocationBasedRouting $true -VoiceRoutingPolicy <PolicyName>

TrunkSet-CsTrunkConfiguration -Identity <TrunkID>-EnableLocationRestriction $true -NetworkSiteID <SiteID>

Enabling the LBR Conferencing AppThe location-based routing conferencing app is disabled by defaultTo enable:

New-CsServerApplication-Identity Service:Registrar:<Pool FQDN>/LBRouting-Priority 0 -Enabled $true -Critical $true-Uri http://www.microsoft.com/LCS/LBRouting

This application also enforces LBR for consultative transfers

Scenarios

Regulatory compliance

Regulatory requirements57+ Countries regulate Voice over IPCountries Include, UAE, India, Egypt, Pakistan, Oman, Qatar, Parts of China, Many African and Asian countries

Regulation usually requires no bypassing of local telephony providers and service providersNo Toll bypass, no Least cost routing, may be in country and/or international

Regulations make exceptions for closed user groups (i.e enterprises, educational institutions etc.) and allow VoIP and video within the user group, even if international

India Telecom RegulationsNo toll bypass / least cost routing allowedNo mixing of calls between Closed User Group and PSTNSingle call cannot combine a leg from the PSTN to a leg over IPCannot Forward, Transfer or Conference between legs

Country divided into calling zones (typically by carrier)Mobile zones behave differently than landline zonesInter-zone calling not allowed over IP for least cost routing

Process for approval of telecom systemEach deployment has to be certified by Telecom Regulatory Authority of India (TRAI) once completed and test cases have to pass to comply with local regulation90+ calling scenarios need to be testedTesting scenarios and LBR will be offered to the service providers to test themselvesMicrosoft has deployed and received certification of our implementation

Implementation detailsGlobal flag: OnUser’s voice policy: LBR-enabledUsages in user voice policy are used for authorization

Network siteDefine one network site for each “campus” and enable LBR restrictionsAssign voice routing policies to network site that only allow local gateway to be used

TrunkEnable LBR on PSTN trunks to enforce LBR on inbound callsDo not enable LBR on PBX trunks to allow “closed user group” callsTrunks without LBR enabled are used when user is remote or in unknown site

Caller IDWhen call is place out at roaming office, replace line URI with local office numberTrunk translation rulesLook for city/areacode from outsideregion and replace

(Optional) Dedicated trunk for LBR callsNew trunk from different mediation server portUnique set of translation rules

LBR Regulatory Compliance LimitationsCall park and response groupsCall flows with these scenarios could violate the regulatory principlesEither a) do not deploy or b) deploy only to users within a single site

Dial-in conferencingBy dialing-in, may create a conference that has PSTN and VoIP users from different sitesFor strict compliance, do not deploy dial-in access numbers and require dial-out

UM RoutingDenied inbound calls are sent to UMFor strict compliance, place the UM server for a group of users in same site as the gateway terminating their DIDs

Consultative TransfersWhen a single mediation server serves multiple trunks (PBX and PSTN), LBR may be enforced when not necessaryDeploy additional mediation servers for trunks to PBX where LBR is not required

Call path optimization

Call path optimizationEven without regulatory requirements, location-based routing can reduce WAN utilization and improve call qualityFor calls with no gateway local to called party, select gateway local to calling partyAllow all inbound callsCan still provide LCR by including least cost routes as higher priority in site voice routing policy

Implementation detailsGlobal flag: OnUser’s voice policy: LBR-enabledUsages in user voice policy are used for authorization

Network siteDefine one network site for each “campus” and enable LBR restrictionsAssign voice routing policies to network site that prefer local gatewayIf desired, include least cost routes in the site voice routing policy

TrunkDo not enable LBR on inbound PSTN trunks to always allow inbound callsDo not enable LBR on PBX trunks to allow “closed user group” calls

ConcernsIs this more complex than justified by the benefits?PowerShell-onlyPotentially-complex voice routing policies created/assigned/maintained for each network site (with gateways)LBR has been added to Lync Dialing Rule Optimizer (http://www.lyncoptimizer.com/)User’s voice policy will be used when remote or at an unknown site

Remote worker routing

Remote worker routingUsers located at poorly-connected branches should not use the branch gateway when remoteSelect datacenter gateway when working remotelyEssentially, same as call path optimization scenario

Implementation detailsSee call path optimization implementation detailsPolicy assigned to user will have preference for trunks located in datacenter where edge servers are located

Local security desk

E9-1-1 and LBRLBR does not apply to E9-1-1If user dials the emergency dial string in the application location policy, routing will be according to the usages in the location policy – LBR configuration will be ignored

Should I use LBR instead of E9-1-1?Calls do not get other emergency call treatment (IM notification)No PIDF-LO

Use E9-1-1 and LBR in conjunctionUse E9-1-1 feature for “real” emergency calls to service provider or ELIN gatewayUse LBR for other internal desks

Local security deskScenario: Per-building or per-campus local security desk must be reached when dialing a common extensionE9-1-1 only supports one emergency numberUsing LBR could enable multiple PSTN emergency numbers

Use LBR to route this number to a local gatewayImplication: Since these are PSTN calls, the security desk number can't be served by Lync

ConcernsVoice routing policy would route common extension to local gatewayBut! Voice routing policy must be complete – it would have to include routes for every other destinationMay conflict with requirements that could be served better by user-based policies

Not the same as location-based normalizationOften, normalizing the extension to a different E.164 number would be betterWould allow security desk to be on LyncThis is not currently possible

Special considerations

Design considerationsWhen using LBR the site routing policy must include a route for all possible calls.It’s possible that a call would be allowed by the user’s policy but, if it isn’t allowed by the site’s policy, it will be blocked.

Trunks are associated with one network siteFor LBR, your campus must be represented as one site.Without this requirement, you are able to create multiple sites with no bandwidth restrictions for the purpose of assigning different location policies to each building on the campus.

Session Objective(s): Explain Lync Server 2013 location-based routing capabilities.Recommend solutions using location-based routing to enable regulatory compliance or optimize call paths.Identify limitations in location-based routing implementations.

Location-based routing can addressmany customer requirementsLocation-based routing must beimplemented with care

Session Objectives And Takeaways

Questions?

Microsoft PavilionDemos, Speakers, Demos, Lync Room System, Experts, Demos, a Bar....and more Demos

ATTENDEE PARTY Wednesday, February 19th

6:30pm-9:30pmHakkasan, MGM Grand

Brought to you by

When it comes to Vegas nightclubs, it doesn’t get any hotter than Hakkasan. And when it comes to opportunities to connect and reasons to party, no one does it better than Lync Conference! Our attendee party has a full lineup: an open bar, awesome food, and one of the best DJs that Vegas has to offer. Don’t miss out on the fun—stop by at 6:30pm and kick off and evening to remember. Come together.

HANDS-ON LABS

You can also access labs on MyLync!

3:00pm – 9:00pm10:30am – 9:00pm7:30am – 9:00pm8:00am –1:30pm

LOCATIONPinyon 3

Monday, February 17Tuesday, February 18Wednesday, February 19 Thursday, February 20

LRS

LOCATIONCopperleaf 12

Wednesday, February 198:30am – 9:45am10:15am – 11:30am1:00pm – 2:15pm2:45pm – 4:00pm4:30pm – 5:45pm

Thursday, February 209:00am – 10:15am10:45am – 12:15pm12:45pm – 2:00pm

MyLync allows you to create a custom experience and network with the Lync Community both online and in person.With MyLync, you can:• Build your own personalized calendar while browsing all available sessions• View breakout session material including PPTs and Videos within

48 hours of each session• Participate in the Community and find people in your social networks

who are attending and interact with speakers• Arrange meetings or social activities• Navigate the Exhibit Hall floor plan and learn more about our Sponsors• Fill out evaluations to win prizes

Log into MyLync at http://mylync.lyncconf.comFor MyLync support, please visit the Registration Desk.*

* Please note that adding a session to your calendar does not reserve a seat. Seating is on a first-come, first-served basis.

Birds of a FeatherBirds of a Feather flock together! Join daily breakfast discussions of relevant topics by sitting in the separately designated areas of the Meal Hall. Seating will be sorted in a different way for each Birds of a Feather breakfast:Wednesday, February 19:Where are you from? Asia/Pacific, Eastern & Central Europe, Latin America, Middle East & Africa, US (West, Central & East) and Canada, Western Europe

Thursday, February 20:What is your interest?Best Practices, Business Value, Clients & Mobility, Lync Meetings and Video, Lync Online, Networking, Platform, Server & Manageability, Voice

Fill out evaluations to win prizesFill out evaluations on MyLync or MyLync Mobile.Prizes awarded daily.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.