Lync Enterprise Voice Core Infrastructure Updates

Lync Enterprise Voice Core Infrastructure Updates
Microsoft Lync 11/13/2018 Lync Enterprise Voice Core Infrastructure Updates Aaron Steele | Microsoft Brian Ricks | BriComp Computers © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Meet Aaron Steele | @steeleaaron
11/13/2018 Meet Aaron Steele Senior Consultant Been with Microsoft for 3 years Focused on Lync and specifically voice In computers and MS technology for 18+ years Started in Higher Education Wife and two kids, lives in Chicago, IL © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Meet Brian Ricks | @bricomp
11/13/2018 Meet Brian Ricks Lead Architect, BriComp Computers Unified communications architect Microsoft Certified Solutions Master Microsoft MVP since 2006 Enterprise Microsoft collaboration solution design, development, configuration, administration and maintenance More than 20 years experience in IT industry Network Infrastructure Corp., Resolute, Phelps, Dodge Independent since 2009 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Setting Expectations Target Audience
11/13/2018 Setting Expectations Target Audience IT and telecommunications professionals who design, plan, deploy, and maintain solutions for unified communications (UC) Experienced professionals that are looking to better understand the new features and capabilities of Lync introduced since RTM © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 Suggested Resources Course 20336, Core Solutions of Microsoft Lync Server 2013 — Course 20337, Enterprise Voice and Online Services with Microsoft Lync Server 2013 — © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Know Your Stuff? Get Certified
Microsoft Lync 11/13/2018 Know Your Stuff? Get Certified Microsoft Certified Solutions Expert (MCSE) – Exam : Core Solutions of Microsoft Lync Server 2013 – Exam : Enterprise Voice and Online Services with Microsoft Lync Server 2013 – Microsoft Learning Partners—Learn from the Pros! – – Find a Class: © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Lync Voice Architecture Overview
Microsoft Lync 11/13/2018 Lync Voice Architecture Overview © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Lync Server High-Level Topology
Public Providers Identity New! Edge More secure federation and interoperability External user ingress Federated Network MIIS AD Edge server UC end points Voic / Archive Hybrid Front-end Exchange Back-end Monitoring  Pool Fewer, consolidated servers Virtualized and higher scale EE pool SCOM File store New! IP-PSTN gateway Mediation Server (optional) DFS Web Access PSTN Reverse proxy Services Consolidated archiving SCOM, AD, DFS Office Web Apps PBX Persistent Chat (optional) CDR/QoE/ Report DB SQL External Perimeter network Internal

Lync Voice Enhancements
Location-Based Routing Support for M:N—MS:GW Session management Improved Caller ID management Improved delegate routing Response Group Manager Support for IPv6 in all Lync components Support for VDI for audio and video Lync Voice Routing enhancements IPv6 VDI

Deployment types On-premises Lync 2013 Cloud Lync Server 2013 Private cloud/dedicated Single domain and directory Users split—server/online Microsoft Office 365, Lync Online Partner-hosted or multi-tenant Enabling gradual migration and coexistence between Lync private and public clouds

Overview of Lync Offerings
Microsoft Lync 11/13/2018 Overview of Lync Offerings Lync Server 2013 on-premises – Full UC including Enterprise Voice May be used with Exchange Online or Exchange Server on-premises Lync Online – IM, Presence, & Meetings without Enterprise Voice May be used with Exchange Online or Exchange Server Lync Hybrid – Lync Server & Lync Online in a shared setup Combining both worlds, on-premises users with Full UC including Enterprise Voice , IM & Presence and Conferencing for Online users. Sharing the same namespace. Lync Hosted – Third-party offering of Lync Server May be used with Exchange Online or Exchange Server. Depending on the hosting provider may include Enterprise Voice functionality © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Voice Routing in Lync A quick recap of the most important elements

Voice Routing 1 2 4 3 5 6 7 8 9 12 11 13 10 14 RFC 3966 Starts with +
User Initiates Call Lync Client Normalizes Normalization Rule Dial Plan User=phone SIP URI 2 Must Match A Rule 4 Global? Emergency Call? No No 3 msRTCSIP-Line msRTCSIP-PrivateLine 5 404: No matching rule 6 Call Park Orbit Range Yes Yes Dialing Behaviors 7 Reverse Number Lookup Policy Creates per User Routing Routing & Authorization No match 8 Match 1. Vacant Number Range 2. Call Park Orbit Range PSTN Usage 3. Voice Policy Routes Route PSTN Usage Location Policy 9 12 Convert # to Local Format PSTN Fallback for CAC and Network Outages 11 Mediation Server and Trunk Configuration 13 403: No route found 10 Announcement or Call Park Application Apply Called Party Prefs Gateway / IP-PBX / SIP Trunk Inbound Routing 14 External Endpoint Receives Call UC Endpoint Receives Call 14

Routing and Authorization
The big picture of the most important elements Voice policies PSTN usages Routes User authorization Class of service Voice feature set Purpose (usage, caller’s intent) Calling location Priority Called number Cost of call 15

Voice Policies Can be assigned per user, per site or global
Microsoft Lync 11/13/2018 Voice Policies Can be assigned per user, per site or global Provides admins with flexibility to control user voice entitlements Call Forwarding, Delegation, Call Transfer, Call Park, Simultaneous Ringing, Team Call, PSTN Rerouting, BW Policy override Malicious call tracing Control Dialing capabilities (Class of Service) by assigning PSTN Usages Not only for users; also useful to address Common Area Device requirements Assign a Voice Policy to a common area phone to prevent misuse and high cost © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 PSTN Usages A PSTN usage record specifies a class of call (such as internal, local, or long distance) that can be made by various users or groups of users in an organization By themselves, PSTN usage records do not do anything. For them to work, they must be associated with the following Voice policies, which are assigned to users Routes, which are assigned to phone numbers © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 Routes A voice route associates destination phone numbers with one or more public switched telephone network (PSTN) gateways or SIP trunks, and one or more PSTN usage records A route is selected based on a matching pattern PSTN Usages control if a user is allowed to use the Route Routes are associated with one or more trunks © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Controlling Gateway Preference
Lync Conference 2013 11/13/2018 Controlling Gateway Preference Multiple trunks in same route Gateway will be selected randomly. Useful when there is no gateway preference and multiple gateways are available for same path to PSTN. Multiple routes in the same usage 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. Routes in different usages Gateway selected based on the order of the usages in the user’s voice policy. Useful for enforcing primary/secondary relationships between gateways. © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Location-Based Routing

Introducing Location-Based Routing
Microsoft Lync 11/13/2018 Introducing Location-Based Routing Location-Based Routing (LBR) is designed to enable compliance with regulatory requirements that restrict toll bypass Routes the call based on the location of the caller Enforce routing of PSTN calls to prevent toll bypass Scoped to specific sites, gateways, and users Delivered in the July 2013 update to Lync Server LBR for PSTN calls was introduced in the February 2013 update The July 2013 update adds support for dial-out conferencing. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Least Cost Routing versus Location-Based Routing
Microsoft Lync 11/13/2018 Least Cost Routing versus Location-Based Routing Least cost routing Route call to the gateway closest to the called party Minimize toll charges (toll bypass) Prioritize the use of the WAN Location-Based Routing 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 . © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Location-Based Routing in Pictures
Microsoft Lync 11/13/2018 Location-Based Routing in Pictures Location A Location B Location A Location B WAN WAN PSTN PSTN GOOD BAD © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Location-Based Routing Capabilities
Microsoft Lync 11/13/2018 Location-Based Routing Capabilities Enforces that outgoing calls must egress from an allowed PSTN gateway in the caller’s voice policy, based on the callers location Can prevent the incoming call to the Lync client if the endpoint is not in the PSTN gateway’s location Lync Conferencing honors LBR policies for PSTN dial-out © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Regulatory Requirements
Microsoft Lync 11/13/2018 Regulatory Requirements 57+ countries regulate VoIP Countries include: UAE, India, Egypt, Pakistan, Oman, Qatar, parts of China, many African and Asian countries Regulation Examples No allowed to toll bypass No allowed to bypass local telephony providers Regulations may provide exceptions for closed user groups (such as enterprises, educational institutions, and so on) and allow VoIP and video within the user group, even if international Designed specifically to enable compliance in India © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

LBR Regulatory Compliance Limitations
Microsoft Lync 11/13/2018 LBR Regulatory Compliance Limitations Call park and response groups 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 Dial-in conferencing 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 UM routing 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 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Support & Configuration

Location-Based Routing Basics
Microsoft Lync 11/13/2018 Location-Based Routing Basics 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 Voice policy that only contains usages Specifically assigned to a site for LBR Contains all allowed usages for that specific site or trunk Unknown Location Location (subnet) that is not known as a Lync Site Trunk Connects gateways and mediation servers Can be enabled for LBR and must be assigned to site © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Pool Support for Location-Based Routing
Microsoft Lync 11/13/2018 Pool Support for Location-Based Routing Pool Version Mediation Server Version Supported Lync Server 2013 February 2013 Cumulative Update Yes Lync Server 2013 No Lync Server 2010 Office Communications Server 2007 R2 Any © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Client Support for Location-Based Routing
Microsoft Lync 11/13/2018 Client Support for Location-Based Routing Client Type Supported Details Lync 2013 Yes Including Lync 2013 February 2013 Cumulative Update Lync 2010 Office Communicator 2007 R2 No Lync Phone Edition Lync Attendant Lync for Windows 8 Lync Mobile 2013 VoIP must be disabled for Lync Mobile 2013 clients if used by users with Location-Based Routing enabled. Lync Mobile 2010 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Configuring Location-Based Routing
Microsoft Lync 11/13/2018 Configuring Location-Based Routing 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> Enable Location-Based Routing and assign a Voice Routing Policy to the Network Site Set-CsNetworkSite -Identity <site ID> -EnableLocationBasedRouting <$true|$false> -VoiceRoutingPolicy <voice routing policy ID> Enable Location-Based Routing through Trunks Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes) New-CsTrunkConfiguration -Identity < trunk configuration ID> Enable Location-Based Routing on the Trunk Set-CsTrunkConfiguration -Identity <trunk configuration ID> -EnableLocationRestriction $true -NetworkSiteID <site ID> © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Configuring LBR (continued)
Microsoft Lync 11/13/2018 Configuring LBR (continued) Enable LBR through Voice Policy Modify the Voice Policy Set-CsVoicePolicy -Identity <voice policy ID> -PreventPSTNTollBypass <$true|$false> Enable LBR Globally Create a Trunk Configuration (Only for PSTN gateways, not Internal PBX routes) Set-CsRoutingConfiguration -EnableLocationBasedRouting $true © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Design Considerations
Microsoft Lync 11/13/2018 Design Considerations When 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 weren’t allowed by the site’s 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. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Logic

Outbound Routing Microsoft Lync 11/13/2018
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 Outbound Routing One policy for authorization and a different policy for routing Authorization Routing decision © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Trunk-to-Trunk Routing
Microsoft Lync 11/13/2018 Trunk-to-Trunk Routing © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Inbound Routing TechReady 17 11/13/2018
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 Conferencing 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. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Sample Scenarios

Incoming PSTN calls Configuration
Microsoft Lync 11/13/2018 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 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Outgoing PSTN calls Routing Authorization Configuration
Microsoft Lync 11/13/2018 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 Routing Authorization 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 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Call Forwarding Configuration Trunk to Site 1 Gateway enabled for LBR
Microsoft Lync 11/13/2018 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 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

M:N Routing

Introduction to M:N Routing
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

M:N Routing 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 IP-PBX Port A Port A1 Trunk 1 Port B Port B1 Trunk 2 Port n Port n1 Trunk n

Trunk & IP-PBX Interworking – Real Life
Microsoft Lync 11/13/2018 Trunk & IP-PBX Interworking – Real Life 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 Media Bypass MED-10 5060 5061 PBX Extension MTP-2 Media Bypass Trunk 2 MED-10<->PBX-10 PBX-10 port : 5061 Signaling IP : PBX-1 Media IP : MTP-2 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

M:N Routing 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 Port B Trunk 1 PSTN Gateway FQDN F Port C Port B Trunk 2 Mediation Server D Gateway G Port C Port E Trunk 3 PSTN Gateway FQDN G

Resiliency with Multiple Mediation Pools
Microsoft Lync 11/13/2018 Resiliency with Multiple Mediation Pools 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 Site 02 Site 01 Lync Pool Mediation Pool SBC sbc1.provider.com Trunk 1 Trunk 2 PSTN MPLS © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

M:N Routing 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 resiliency—both 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.

Session Management

Session Management “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

Sample Scenarios Routing of IP-PBX Calls to PSTN via Lync
Microsoft Lync 11/13/2018 Sample Scenarios Routing of IP-PBX Calls to PSTN via Lync Incoming call from the PBX trunk Validate incoming trunk associated PSTN usages Determine a route Apply outbound translation rules Route to outgoing gateway trunk Routing of IP-PBX Calls to Another IP-PBX System via Lync Incoming call from the PBX trunk Validate incoming trunk associated PSTN usages Determine a route Apply outbound translation rules Route to outgoing PBX trunk via Lync © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Session Management 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

Configuring Session Management
Microsoft Lync 11/13/2018 Configuring Session Management Using the Lync Management Shell Configure a Voice route Add a PSTN usage to a trunk configuration: New -PSTNUsages property has been added to CSTrunkConfiguration Or through the Lync Control Panel New-CsVoiceRoute -Identity RedmondRoute Set-CsTrunkConfiguration –Identity “TrunkId” © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Microsoft Lync 11/13/2018 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

11/13/2018 © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

Lync Enterprise Voice Core Infrastructure Updates

Similar presentations

Presentation on theme: "Lync Enterprise Voice Core Infrastructure Updates"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Lync Enterprise Voice Core Infrastructure Updates

Similar presentations

Presentation on theme: "Lync Enterprise Voice Core Infrastructure Updates"— Presentation transcript:

Similar presentations

About project

Feedback