Identity

New!

Public Providers Edge server UC end points

Front-end Back-end

Edge
AD

MIIS

Federated Network

Voicemail/ Archive
Exchange

More secure federation and interoperability External user ingress

Monitoring
SCOM

EE pool Hybrid
New!

Pool

IP-PSTN gateway

Mediation Server (optional)

File store
DFS

Fewer, consolidated servers Virtualized and higher scale

Reverse proxy PSTN

PBX Persistent Chat (optional)

Web Access
Office Web Apps

Services

CDR/QoE/ Report DB

Consolidated archiving SCOM, AD, DFS

SQL

External

Perimeter network

Internal

Routing enhancements Lync Voice

Location-Based Routing Support for M:NMS:GW Session management Improved Caller ID management Improved delegate routing Response Group Manager Support for IPv6 in all Lync components

IPv6

VDI

Support for VDI for audio and video

On-premises
Lync Server 2013 Private cloud/dedicated

Lync 2013
Single domain and directory Users splitserver/online

Cloud
Microsoft Office 365, Lync Online Partner-hosted or multi-tenant

May be used with Exchange Online or Exchange Server on-premises

May be used with Exchange Online or Exchange Server

Combining both worlds, on-premises users with Full UC including Enterprise Voice , IM & Presence and Conferencing for Online users. Sharing the same namespace.

May be used with Exchange Online or Exchange Server. Depending on the hosting provider may include Enterprise Voice functionality

1 RFC 3966
Dial Plan

Lync Client Normalizes

No Global?

Starts with +

User Initiates Call SIP URI

User=phone

Must Match A Rule

4
404: No matching rule

Normalization Rule Normalization Rule Normalization Rule

2
No

Emergency Call?

5
Dialing Behaviors

Call Park Orbit Range 6 msRTCSIP-PrivateLine

msRTCSIP-Line

Yes

Yes

Routing & Policy Creates Authorization per User Routing

Reverse Number Lookup No match 3. Voice Policy Routes

8 12
Location Policy

Match

1. Vacant Number Range 2. Call Park Orbit Range PSTN Usage PSTN Usage PSTN Usage

11

PSTN Usage Route Route Convert # Route Route to Local Format

PSTN Fallback for CAC and Network Outages Apply Called Party Prefs

10

Announcement or Call Park Application

403: No route found

13

Mediation Server and Trunk Configuration Gateway / IP-PBX / SIP Trunk Inbound Routing

14

External Endpoint Receives Call

UC Endpoint Receives Call

9

The big picture of the most important elements

Voice policies

PSTN usages

Routes

User authorization Class of service Voice feature set

10

Purpose (usage, callers intent) Calling location Priority

Called number Cost of call

Call Forwarding, Delegation, Call Transfer, Call Park, Simultaneous Ringing, Team Call, PSTN Rerouting, BW Policy override Malicious call tracing

Assign a Voice Policy to a common area phone to prevent misuse and high cost

Voice policies, which are assigned to users Routes, which are assigned to phone numbers

Gateway will be selected randomly. Useful when there is no gateway preference and multiple gateways are available for same path to PSTN.

Gateway selected based on matching pattern. If multiple routes match, do not rely on route ordering for enforcing preference. Used when different gateways are used for different called numbers but all belong to the same class of service.

Gateway selected based on the order of the usages in the users voice policy. Useful for enforcing primary/secondary relationships between gateways.

LBR for PSTN calls was introduced in the February 2013 update The July 2013 update adds support for dial-out conferencing.

Routing
Route call to the gateway closest to the called party Minimize toll charges (toll bypass) Prioritize the use of the WAN

Location-Based

Route call to the gateway closest to the calling party Minimize use of WAN Enable compliance with regulations that do not allow toll bypass

Toll Bypass Use the own (WAN) infrastructure as much as possible Egress to the PSTN closest to the destination Avoid international (costly) PSTN charges

Location-Based Routing

GOOD

BAD

Enforces that outgoing calls must egress from an allowed PSTN gateway in the callers voice policy, based on the callers location Can prevent the incoming call to the Lync client if the endpoint is not in the PSTN gateways location Lync Conferencing honors LBR policies for PSTN dial-out

57+ countries regulate VoIP

Countries include: UAE, India, Egypt, Pakistan, Oman, Qatar, parts of China, many African and Asian countries No allowed to toll bypass No allowed to bypass local telephony providers

Call park and response groups

Dial-in conferencing UM routing

Call flows with these scenarios could violate the regulatory principles Either a) do not deploy or b) deploy only to users within a single site

Dialing in may create a conference that has PSTN and VoIP users from different sites For strict compliance, do not deploy dial-in access numbers and require dial-out
Denied inbound calls are sent to UM For strict compliance, place the UM server for a group of users in same site as the gateway that terminates their DIDs

Consultative transfers

When a single Mediation Server serves multiple trunks (PBX and PSTN), LBR may be enforced when not necessary Deploy additional Mediation Servers for trunks to PBX where LBR is not required

Site

One or more Lync subnet(s) assigned to a location Uses existing network sites as defined for LIS, Media Bypass and E911

Voice Routing Policy Unknown Location

Trunk

Voice policy that only contains usages Specifically assigned to a site for LBR Contains all allowed usages for that specific site or trunk Location (subnet) that is not known as a Lync Site

Connects gateways and mediation servers Can be enabled for LBR and must be assigned to site

Pool Version Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 February 2013 Cumulative Update

Mediation Server Version Lync Server 2013 February 2013 Cumulative Update Lync Server 2013 Lync Server 2010 Office Communications Server 2007 R2

Supported Yes No No No

Lync Server 2013 February 2013 Cumulative Update

Lync Server 2013 February 2013 Cumulative Update

Lync Server 2013 Lync Server 2010

Office Communications Server 2007 R2

Any Any
Any

No No
No

Client Type Lync 2013 Lync 2010 Office Communicator 2007 R2 Lync Phone Edition Lync Attendant Lync for Windows 8 Lync Mobile 2013 Lync Mobile 2010

Supported Yes Yes No Yes Yes No No Yes

Details Including Lync 2013 February 2013 Cumulative Update

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

Enable Location Based Routing for Network Sites Create the Voice Routing Policy

New-CsVoiceRoutingPolicy -Identity <voice routing policy ID> -Name <voice routing policy name> -PstnUsages <usages> Set-CsNetworkSite -Identity <site ID> -EnableLocationBasedRouting <$true|$false> -VoiceRoutingPolicy <voice routing policy ID>

Enable Location Based Routing and assign a Voice Routing Policy to the Network Site Enable Location Based Routing through Trunks Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes) Enable Location Based RoutingOn the Trunk

New-CsTrunkConfiguration -Identity < trunk configuration ID> Set-CsTrunkConfiguration -Identity <trunk configuration ID> -EnableLocationRestriction $true -NetworkSiteID <site ID>

Enable LBR through Voice Policy Modify the Voice Policy

Set-CsVoicePolicy -Identity <voice policy ID> -PreventPSTNTollBypass <$true|$false>

Enable Location Based Routing Globally Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes)

Set-CsRoutingConfiguration -EnableLocationBasedRouting $true

When using LBR, the site routing policy must include a route for all possible calls
Its possible that a call would be allowed by the users policy, but if it werent allowed by the sites policy it would be blocked.

Trunks are associated with one network site

For LBR, your campus must be represented as one site if using centralized SIP Trunks.

One policy for authorization and a different policy for routing

Authorization

Routing Decision

Start

Is source trunk LBR enabled?

No

Is request FWD/XFER/ Simulring?

Yes

Yes

No Use the usages specified in the trunk config Use the usages of the user s voice policy

Use usages from source trunk associated site

Select next applicable usage. Yes

Select next applicable usage.

Yes

Are there additional usages?

No

No Are source and destination trunks sites the same? Are source and destination trunks sites the same?

Are additional usages in the site?

No

Is destination trunk LBR enabled?

Yes

Do not allow call

No

No
Yes

Yes Normal Processing

Do not allow call

Stop

Start

Is Global LBR switch on?

Yes

Is from Phone?

Yes

Is source trunk LBR ?

Yes

Get site associated with the trunk

No No

No

Route to endpoint

Yes

Is endpoint in the gateway site?

No

Route to UM

Stop

The LBR conferencing application ensures that a single conference does not contain VoIP users from different sites and PSTN dial-out.
If there are users in a given conference joining via Lync VoIP clients from a single network site, the following endpoints will be allowed to join the conference: a PSTN endpoint, another Lync VoIP client user from the same site, another Lync VoIP client user from a different site, or a Lync VoIP client user from an unknown network site.

If there are organizers or participants from different or unknown network sites in a given conference, a PSTN endpoint will not be allowed to join the conference via a trunk that is enabled for Location-Based Routing.
If there are organizers or participants from a single site and participants joining via PSTN in a given conference, a Lync client endpoint from a different site will not be allowed to join the conference.

Incoming PSTN calls

Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location

Behavior for Incoming calls through Site 1 Gateway Calls to Users in Site 1 OK Calls to Users in Other Sites Blocked Calls to Users without a location Blocked

Outgoing PSTN calls

Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location Site 1 Voice Routing Policy -Route through Site 1 Gateway Lync User 2 Voice Policy - Route through Site 1 Gateway Lync User 1 Voice Policy - Route through Site 2 Gateway

Behavior for Outgoing calls Calls from Lync User 2: Route through Site 1 Gateway Calls from Lync User 1 Do not route through Site 2 Gateway Route through Site 2 Gateway instead

Call Forwarding
Configuration Trunk to Site 1 Gateway enabled for LBR Site 1 Gateway associated to Site 1 Location Lync User 2 forwards calls to Lync User 3 Lync User 1 forwards calls to Lync User 4 Behavior for Call Forwarding Incoming call to Lync User 2 Forwarded to Lync User 3 Incoming call to Lync User 1 Forwarding to Lync User 4 NOT allowed

Microsoft Office Communications Server 2007 R2

One Mediation Server (MS) was associated with one PSTN gateway and vice versa (1:1)

Lync Server 2010

Multiple PSTN gateways can be associated with the same MS pool (1:N); a single PSTN gateway is associated with a single MS pool; a single SIP listening port on the MS and on the gateway are used in the association

Lync Server 2013

Multiple PSTN gateways can be associated with the same MS pool, also a particular PSTN gateway can be associated with multiple MS pools or the same MS pool with multiple unique associations

Trunks and IP-PBX interworking

Trunks associate Mediation Servers with PSTN Gateways Multiple trunks can be defined between Mediation Server and PSTN gateway representing IP-PBX SIP termination. Each trunk will be associated with the appropriate route for outbound calls from MS to IP-PBX. For inbound calls, per-trunk policy will be applied. Trunk configuration will be scoped globally or per trunk; similarly, dial plan can be scoped per trunk. Representative media IP is a per-trunk parameter.

Mediation Server
Port A Port B Trunk 1 Trunk 2 Port A1 Port B1

IP-PBX

Port n

Trunk n

Port n1

Typical PBX deployment: Central Call Control (PBX-10) Decentralized Media Termination Points (MTPs / Gateways) Technical requirements Use MTPs on same site as Lync Client, keep media local Enable Media Bypass Deployment and configuration: 1. Define PBX-10 as PSTN Gateway Use MTP1 as Alternate Media IP-Address The First Trunk is created automatically 2. Add Additional trunks for remaining MTPs: Use different PBX Listening ports 3. Use PS to define RepresentativeMediaIP for each MTP/Trunk

Trunk 1 MED-10<->PBX-10 PBX-10 port : 5060 Signaling IP : PBX-1 Media IP : MTP-1

PSTN Gateway PBX-10

PBX Extension
MTP-1

PBX-10

MED-10

5060 5061

Media Bypass

PBX Extension
MTP-2

Media Bypass
Trunk 2 MED-10<->PBX-10 PBX-10 port : 5061 Signaling IP : PBX-1 Media IP : MTP-2

Trunks and resiliency

Gateway F connects to two Mediation Servers Resiliency does not require multiple MS listening ports. The main reason for multiple MS listening ports is interoperability. Fully supports TLS Example Port C : 5061, can be used as the MS listening port for Gateway 1 and Gateway 2 Port D : 5068 can be used on SAME MS for a different gateway or IP-PBX if required

Mediation Server C Gateway F

Port A Trunk 1 Port B

PSTN Gateway FQDN F Mediation Server D Gateway G

Port C Trunk 3 Port E

PSTN Gateway FQDN G

PSTN

SBC sbc1.provider.com

Trunks & Gateways

Separation of Configuration between Gateways and Trunks Gateways define the next hop Trunks define the relation between Mediation Server and Gateway Allows for TLS, eliminates the need for Virtual Gateways Allows for Gateway-specific inbound policies
Trunk 1 MPLS Trunk 2

Site 01
Mediation Pool

Site 02
Mediation Pool

Lync Pool

Trunk definition
In Lync Server 2013, a trunk is defined as a combination of: MS FQDN Mediation SIP listening port Gateway FQDN Gateway SIP listening port This approach provides for: Better resiliencyboth service and on-premises scenarios

Better interworking with IP-PBXs for bypass

Using TLS plus Secure Real-Time Transport Protocol (SRTP) for multiple SIP trunks to the same SBC FQDN When outbound routing matches a dialed PSTN number to a route, the route will consist of a list of trunks.

Contrast this approach with Lync 2010, where a route consisted of a list of gateways.

Better integration with systems certified to connect with Lync A possible alternative for PBX integration scenarios Lync Server can support call routing from an incoming trunk to an outgoing trunk to provide routing functionalities to other systems By enabling intertrunk routing, the following routing paths (among others) are enabled:
Incoming PSTN calls to an IP-PBX system via Lync Outgoing IP-PBX calls to a PSTN network via Lync Outgoing IP-PBX calls to another IP-PBX system via Lync

Inbound Trunk

PSTN Usage

Lync Pool

Route

Outbound Trunk

Qualified IP-PBX

Lync Mediation Server

Trunk

Lync Mediation Server

Trunk

Qualified Gateway
PSTN

MEDIA

Inbound Trunk

PSTN Usage

Lync Pool

Route

Outbound Trunk

PBX User

Qualified IP-PBX

Lync Mediation Server

Trunk

Lync Mediation Server

Trunk

Qualified IP-PBX

PBX User

MEDIA

Lync supports the association of a set of PSTN usages on an incoming trunk to determine a call route to an outgoing trunk Intertrunk configuration remains familiar for the administrator with the use of existing routing configuration concepts Media bypass in intertrunk routing calls is supported Intertrunk routing call authorization scope is at the trunk level
The same call authorization applies to all calling endpoints connected via the trunk

Using the Lync Management Shell

New-CsVoiceRoute -Identity RedmondRoute -PstnUsages @{add=Redmond"} -PstnGatewayList @{add="PstnGateway:redmondgw1.contoso.com"}

Set-CsTrunkConfiguration Identity TrunkId -PstnUsages @{add=Redmond}

Or through the Lync Control Panel

Appendix: Implementation

Create a voice routing policy New-CsVoiceRoutingPolicy Identity <PolicyID> Name <PolicyName> -PstnUsages <Usage1>, <Usage2> Users assigned voice policy is used for authorization
Voice routing policy assigned to site is used to select gateway

Global flag
Set-CsRoutingConfiguration -EnableLocationBasedRouting $true

Users voice policy

Set-CsVoicePolicy <PolicyName> -PreventPSTNTollBypass $true

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

Trunk
Set-CsTrunkConfiguration -Identity <TrunkID> -EnableLocationRestriction $true -NetworkSiteID <SiteID>

The Location-Based Routing conferencing app is disabled by default To enable:

This application also enforces LBR for consultative transfers