Lync 2010 Voice Deployment
Download as PPTX, PDF5 likes1,441 views
The document discusses various voice deployment features in Microsoft Lync Server 2010 including call park, unassigned number routing, E911 location services, private lines, caller ID controls, phone infrastructure requirements, voice routing considerations, and mediation server consolidation. Planning items covered include branch resiliency, datacenter resiliency, call admission control, topology changes, enhanced 911 for North America, analog devices, common area phones, and malicious call trace.
Lync 2010 Voice Deployment
- 1. Microsoft® Lync ™ Server 2010 Voice Deployment Byron Spurlock Founder Architect - Quadrantechnologies Byrons@Quadrantechnologies.com http://Quadrantechnologies.wordpress.com/2011/
- 2. Agenda • Review Lync 2010 voice topology • Planning and overview of new voice features in Lync 2010 – Call park – Unassigned number routing – E9-1-1 – Private Line – Caller ID – Monitoring – Common Area Phones / Phone Infrastructure – Analog Devices / Phones – Trunk Translations – Mediation Server Consolidation / Multiple Gateways – Malicious Call Trace – Exchange UM • Voice routing dialplan considerations • Branch Considerations • Datacenter Considerations
- 3. Lync 2010 Voice Topology
- 4. Archiving MSN DMZ Monitoring PIC UC AOL XMPP Yahoo Endpoints Remot e UC AD DNS Users Pool Front End (incl. Mediation) End AV Conf. Back Federate Edge d Services Business SIP es Trunkin ExUM g Mediation Server IP-PBX On-premise Analog Devices PSTN or online Media GW / SBA Circuit Packet
- 5. Lync 2010 Voice Feature Planning
- 6. Voice Investments Lync Server “OCS 2007 • Branch Resiliency (SBA) R2” • Datacenter Resiliency • Call Admission Control “OCS 2007” • Single Number reach • Call park, Unassigned # • Topology changes • Attendant Console • Media bypass • Delegation/TeamCall • Enhanced 9-1-1 for North • “Anywhere Access” • Response Groups America (NA) • IM and Rich Presence • Session Initiation Protocol • Routing changes • Common voice (SIP) Trunking • Analog devices features • Dial-in audio conferencing • Common area phones • Unified messaging • Higher definition video • Private line • Audio and video • UC Workflow activities • Malicious Call Trace (MCT) conferencing • Larger device portfolio • Desktop integration 6
- 7. Call Park • Call Park allows an Enterprise Voice user to put a call on hold from one endpoint and then retrieve the call later by dialing an internal number • Clients Supported • Clients that can Park Calls - Lync 2010, Lync 2010 Attendant, Lync 2010 Phone Edition • Clients that can retrieve calls – Above plus OCS 2007 R2 Clients, IP Common Area Phones, Non Lync endpoints (E.g. PBX Phones) • Orbit Range • Call Park uses orbits (internal numbers not assigned to users) for parking calls • Orbits are scoped at the pool level by assigning the range to the Call Park Service running on the front ends • Have enough orbits so that any one orbit is not reused too quickly • Assigning DID numbers as orbit numbers is not supported • No need to define an orbit range for every pool but must disable call park service on pools that do not have ranges defined • Comparison/Caveats • No parking in a known destination or at another extension • No pickup from any ringing extension
- 8. Unassigned Numbers - Announcements • Handles numbers that are valid for your organization but not assigned to a user or phone • Transfer these calls to a predetermined destination (phone number, SIP URI, or voice mail) or play an audio announcement or both • Create and Manage an Unassigned Numbers List For Example : • Unprovisioned Numbers • Decommissioned Numbers • Blocked Numbers
- 9. Location and Enhanced 911 • Lync now includes a Location Information Server (LIS) for clients to acquire locations • Location used for Presence, Emergency Routing, or both • Populating LIS database with (in order of preference): • Wireless Access Point (BSSID) • LLDP Port • LLDP Switch • Subnet • MAC • Powershell manual or CSV (no Lync Control Panel Support) for configuring LIS • Location Policy is needed for enabling E911 and routing • User • Subnet • Emergency Calls are routed via SIP to Emergency Service Provider – includes the location • Include Security Desk IM alter and conference • Requires obtaining routing service from a provider • Can be used for location based emergency routing outside of United States
- 10. Private Line • A private line is a phone number that is not published in Active Directory Domain Services (AD DS) and, as a result, is not readily available to other people. • Private lines do not include assigning the user a second Line URI or SIP address but merely a specific value for the PrivateLine property. • Private lines bypass most in-bound call routing rules; for example, call forwarding, team call, delegation, team ring, do not disturb, and Response Groups. However, when simultaneous ringing is enabled on a user’s primary line, it is also enabled on the private line. • Private lines do not work if a user on OCS 2007 R2 calls the private line of a user on Lync Server 2010. OCS 2007 R2 cannot perform a reverse phone number lookup on the private number resulting in the call failing. • Private lines work only on inbound calls. Users cannot use the private line to make an outbound call. • Private lines will send voicemail to the same Exchange mailbox as the primary phone number.
- 11. Caller ID Presentation Controls • Admins can natively control what Caller ID is presented to the receiving party (PSTN/PBX): • Per user/group controls to suppress/alter calling party number by a route setting • Granular controls based on callers and destination number: • Alice calls an external PSTN number, caller ID is presented as +1 425 555 0100 • Alice calls an internal PBX number, caller ID is presented as +1 425 555 2302 • Override for “simultaneous ringing”: Bob calls Alice, who has caller id masked for external calls and also has simultaneous ringing configured; Bob’s caller-id is presented to Alice’s mobile device
- 12. Caller ID Presentation Controls
- 13. Monitoring • Deployment not complete until you deploy monitoring • Monitoring provides QoE reports and Call Accounting (CDR) • You can collocate Monitoring Server with Archiving Server • Scalability : • 250,000 Users per Monitoring Server • CDR database grows 31.5 KB per user per day • QoE database grows 28 KB per user per day • Run the Monitoring Server databases in a separate instance from other databases
- 14. Common Area Phone Support •Enables low-cost IP phones to be placed in common (shared) areas. • Base Functionality • Ability for admin to pre-provision phones for installation by Move-Add-Change (MAC) tech • Ability to configure call control behavior • Ability to block external usage, compromised accounts • Low user intervention e.g. 100% recovery from power outages • Support for hot-desking scenario • Temporary use by an enterprise voice user • Can toggle from a common area to hot desk user
- 15. IP Phone Infrastructure Requirements • Power-over-Ethernet (PoE) supported • Not required but make sure to order adapters • DNS requirements are roughly the same as R2 • Used to discover the Lync pool • DHCP requirements are new - when using PIN auth since DNS lookups can’t be done • Enterprise DHCP servers must support option 43 with MSUCClient vendor class and option 120 • Registrar can be enabled to provide these options
- 16. Voice Routing – Trunk Translations Centrally manage number formatting prior to routing to PBX/PSTN Alice calls +44221234567; based on route translation pattern, called number formatted to 01144221234567 when using GW in Redmond Bob calls +44221234567; based on route translation pattern, called number formatted to 0221234567 when using GW in London
- 17. Mediation Service Colocation Lower TCO and better quality with two enhancements • Multiple Gateways per Mediation Service • Routes point to a Gateway • Outbound Routing uses topology document used to find an appropriate Mediation Service • Mediation Service uses the GW-FQDN in the Request-URI to route to appropriate Gateway •With Media Bypass allows Lync Server 2010 consolidation of most Route GW Mediation Route_US LAX_GW resources at the Data Center Route_EUR DE_GW1 DE_GW2 Route_APAC SYD_GW
- 18. Malicious Call Trace • Lync provides the end-user the capability of tagging the prior call as a malicious call. • Supported in Lync, Lync Phone Edition & Attendant Console. • Tagging is reflected in the backend CDR database, enabling the Lync Server administrator to take action on the call.
- 19. Exchange Unified Messaging (UM) • Only supported voice mail solution for Lync users • Lync supports Exchange UM 2007 SP1 and beyond • Do not separate UM and Mailbox servers over the WAN • MAPI traffic is less tolerant of latency than VoIP in this scenario • UM servers in separate forests from the Lync forest is a supported topology • Need to ensure the EUM settings in the proxyaddress of the user objects are synched to the Lync forest • Hosted EUM as part of O365 is also now supported • Can integrate with both simultaneously • EUM enablement setting on the user object is needed • User Move • Lync Powershell • Need to configure Edge Server for a shared domain
- 21. Dial Plans • Known as the location profile in OCS 2007 R2 • A set of normalization rules that translate dial strings to full, unique numbers (E.164) that are required by the routing and authorization applications of Lync • Lync clients normalize dialed numbers before they are sent to the server • Normalization rules are specified using regular expressions 21
- 22. Planning for Dial Plans • Identify all areas within the organization that have local dialing requirements • Identify the valid number patterns for each • Try to standardize on an organization wide scheme • Determine the Dial Plan Scoping strategy • Dial Plans are obtained by UC clients through the inband provisioning process via the scope of the Dial Plan policy
- 23. Dial Plan Scope • The most specific policy available will be applied • User policy will be assigned or it will be set to <Automatic> Global Contoso to allow selection from Pool, Site, or Global policies Site Chicago London • Generally user based scopes are preferred even for Pool Chicago- Chicago- Dublin-1 survivable branches 1 2 – Consistent operational practice User – Users won’t pick up different Dial Plans when roaming or the SBA goes offline • Pool scopes are for PSTN gateways and Registrar’s of a Pool – Mediation Server appends on INVITE of incoming calls from gateway for example 23
- 24. Voice Policies • Control of user voice features – Call Forwarding – Delegation – Call Transfer – Call Park – Simultaneous Ringing – Team Call – PSTN Rerouting – BW Policy Override – Malicious Call Tracing • Associated to PSTN Usages – what calls are authorized 24
- 25. Voice Policy Scope • The most specific policy available will be applied • Generally user based scopes are preferred even for Global Contoso survivable branches – Consistent operational practice – Users won’t pick up different Site Chicago London Voice Policies when roaming or the SBA goes offline • The PSTN Usages provide the link between the user and User outbound routes – at least one is required. • The ordering of PSTN usages is important because outbound routing does usage matching from the top down. 25
- 26. Planning for PSTN Usages • PSTN Usages are just call permission descriptive labels – These are generally based on the PSTN cost • Identify all call permissions that are required in the organization – create a PSTN Usage for each • Should be contextual – Local in context such as Atlanta Local – Regional in context like US Long Distance • The result should be that there are PSTN Usages defined that meet the dialing authorization needs of the organization • Can establish priority of routes by ordering usages that can route the same called number
- 27. Planning Voice Routes • Routes are needed to route the destination numbers listed in the Dial Plans – There should be no Dial Plan numbers that don’t match users, orbits, unassigned numbers, or routes – Regular expressions are also used in Routes to specify the dialed number to match • Each Route is required to have the FQDN of one or more gateways which support the route – Calls will be evenly distributed between multiple gateways in a given route • Each Route gets assigned the PSTN Usage records that users must have in order to call the numbers served by the Route – US Long Distance – Route resiliency can be done with multiple Usage’s • User’s first Usage grants “Local Calling” • User’s second Usage grants “Long Distance Calling” – can also reach local numbers • Least Cost Routing is supported by associating numbers to specific gateways – Europe countries codes could egress from a single gateway for example
- 28. Call Authorization and Routing Voice Policies PSTN Usages Routes • Call • Purpose (usage,• Called number authorization caller’s intent) • Cost of call • Voice feature • Priority set
- 29. High Level Outbound Routing Logic 1. Dialed number is normalized to an E.164 number 2. Reverse number / user lookup is done • If matched then route to the user’s SIP URI 3. Check Call Park orbit and Unassigned Number ranges • If matched then route to appropriate service 4. Check user’s first PSTN Usage and check each route that contains this Usage and matching destination number • If matched that route to Mediation server for the gateway • Perform appropriate trunk translations for the gateway 5. Iterate through user’s additional Usage’s • If no route match return a 403 (bad config)
- 30. Lync 2010 Branch Deployments
- 31. Branch Deployment Options Large Branch (>1000 users) Survivable Branch Server (or SE Server) AND Separate Media Gateway 1000 SBA Lync Medium Branch (25-1000 users) PSTN / WAN SBA 500 25 Small Branch (<25 users) No Local Infrastructure Or gateway (GW) Only 31 Users
- 32. Lync 2010 Voice High Availability
- 33. Resiliency Architecture Branch Office Registrar Data Center - EE Pool 1 Backup Presence Active Directory Registrar SBA Conferencing Pool AD & DNS Joe’s Primary Registrar = SBA., User Services = EE Pool1 Registrar (Registration Data Center - EE Pool 2 & Routing) Backup Active Directory Registrar Presence AD & DNS Pool Conferencing Registrar (Registration Alice’s Primary Registrar & Routing) & User Services = EE Pool 2 Bob’s Primary Registrar & User Services = EE Pool 1 Architecture: 1. Each user has a “Primary Registrar Pool”. Each Registrar Pool can have a “Backup Registrar Pool” 2. User’s client discovers a Registrar Pool through DNS SRV. Directed to “Primary & Backup Registrar Pool” 3. Backup Registrar heart-beats Primary Registrar. If heart-beat not received within Configurable Failover Interval (default = 120 sec for branch offices), Backup starts accepting client registrations 33
- 34. Lync 2010 Voice Administration
- 35. Built-in Roles Built-In Role Exchange Equivalent Notes CSAdministrator Organization Management Top level; Can assign roles Archiving configuration and Retention Management, Legal CSArchivingAdministrator policies– exclusive access to Hold some functions Read-only view with access to CSHelpDesk HelpDesk troubleshooting tasks Manage, monitor, troubleshoot CSServerAdministrator Server Management services, including start, stop, drain Provision, move, assign policies CSUserAdministrator Mail Recipients to users View Only Organization View only access to CSViewOnlyAdministrator Management configuration, health CSVoiceAdministrator N/A Voice settings and policies CSResponseGroupAdministr Response Group Service (RGS) N/A ator management 35 CSLocationAdministrator N/A Lowest level E911 rights
- 36. Summary: Lync 2010 Voice Planning • Voice Topology • Voice Features and Overview • Voice Dial Plan Considerations • Branch Office Considerations • Datacenter Considerations 36
- 37. © 2011 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. 37 MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.