This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
Copyright © 2011 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Lync, Windows, and Windows PowerShell are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
This chapter is part of the Microsoft Lync Server 2010 Resource Kit book that is currently being developed. Chapters will be available for download while this book is being completed. To help us improve it, we need your feedback. You can contact us at nexthop@microsoft.com. Please include the chapter name.
For information about the continuing release of chapters, check the DrRez blog at http://go.microsoft.com/fwlink/?LinkId=204593.
Contributors
Project Manager: Susan S. Bradley
Content Architect: Rui Maximo
Chapter Lead: Andreas Strebel
Writers: Mahendra Sekaran, Radu Constantinescu, Roy Kuntz
Technical Reviewers: Abdul Waraich, Ken Araujo, Ling (Lingzhi) Cao, Oscar Antezana Chavez, Robbie Bikdash, Subbu Chandrasekaran, Tony Bell, Vassili Kaplan
Lead Editor: Janet Lowen
Contributing Editors: Jim Bradley, Kelly Fuller Blue
Art Manager: Jim Bradley
Production Editor: Kelly Fuller Blue
Substantive Changes
Change
Location
Additions made to Figure 15 based on reader feedback.
New call admission control (CAC) content.
Page 28
Pages 9-11 and 19-25
Table of Contents
Contributors 4
Substantive Changes 5
What Is New in Enterprise Voice? 8
Scenarios for Enterprise Voice 8
Private Line 8
Call Admission Control 9
Call Park Application 11
Call Park and Retrieve 11
Ringback 12
Transfer to Fallback Destination 12
E9-1-1 12
Publishing Location to Contacts 12
Providing Location with Emergency Calls 15
Routing Enhancements 15
Support for Multiple Gateways per Mediation Server 15
Pre-Routing Number Translations 17
Caller ID Management 18
Analog Devices 18
Internals for Enterprise Voice 18
Private Line 18
Understanding Private Line Characteristics 19
Understanding Private Line Configuration 19
Understanding Private Line Routing 19
Call Admission Control 19
Bandwidth Policy Service Synchronization 22
Voice Applications Overview 25
Routing Requests to Voice Applications 26
Call Park Application 26
Understanding the Call Flow for Call Park 29
Understanding the Retrieve Call Flow 29
Understanding the Call Flow for Ringback and Transfer to a Fallback Destination 30
Orbit Management 31
E9-1-1 Locations 32
Enabling E9-1-1 39
E9-1-1 Routing 45
Routing Enhancements 48
Supporting Multiple Gateways per Mediation Server 50
Number Translations Prior to Routing 50
Caller ID Controls 51
Analog Devices Routing 52
Summary 54
Additional Resources 54
What Is New in Enterprise Voice?
Microsoft® Office Communications Server 2007 and Communications Server 2007 R2 introduced some of the core features needed to address Enterprise Voice requirements. Microsoft® Lync™ Server 2010 builds on those solid investments and introduces several features that are required by an enterprise to consider Lync Server 2010 as a viable replacement option for their telephony infrastructure. The following list highlights new voice features introduced in Lync Server:
· Call park and retrieve
· Call admission control
· Enhanced 9-1-1 (E9-1-1)
· Private line
· Routing enhancements
Scenarios for Enterprise Voice
For each feature listed in the previous section, the following sections describe one or several scenarios that illustrate the behavior of the feature. The scenarios provide the context for how a feature is often used. The “Internals for Enterprise Voice” section later in this chapter gets into the details about how the features work.
Private Line
The private line feature enables users to override delegation and other redirection features so they can be reached directly on a private line. For example, Marco is an executive at Contoso, Ltd. His IT administrator has configured the delegation feature on Marco’s phone line so all his incoming calls go to his assistant. Marco also has an additional “secret” number. This is the number Marco shares with Mike, an executive at Fabrikam Inc. Whenever Mike calls Marco’s private number, Marco’s delegation feature is overridden and he is able to see that the incoming call is on his private line (Figures 1 and 2). If Marco does not answer the call, the call is redirected to his unified voice mail box.
Figure 1. Marco receiving a private call from Mike
Figure 2. Marco in a private call with Mike
Call Admission Control
Lync Server supports highly adaptable audio (RTAudio) and video (RTVideo) codecs that adjust to meet fluctuating network conditions. To prevent degradation of audio and video call quality when the network link is oversubscribed, Lync Server introduced a new feature, the call admission control (CAC) service. CAC prevents users from establishing calls that might degrade the call quality of the network. CAC helps prevent unexpected call spikes from adversely affecting the entire network, line of business applications, and quality of current calls. CAC prevents call quality degradation by limiting the number of concurrent calls over limited bandwidth links, such as wide area networks (WAN).
When establishing a new call that will oversubscribe a WAN link, CAC re-routes the call through the public switched telephone network (PSTN) gateway or offloads the media portion of the call over the Internet. This approach offers greater flexibility for handling traffic spikes that can oversubscribe the network. When re-routing calls, CAC first attempts to redirect the audio through the Internet. If this fails, CAC attempts to re-route the call through the PSTN gateway. If PSTN gateway re-routing is not possible, the call is forwarded to voicemail. Calls sent to voicemail are not subject to bandwidth checks, because voicemail sessions are not subject to CAC.
For a description of how CAC works, see the article, “Call Admission Control in Lync Server 2010,” at http://technet.microsoft.com/en-us/library/ff731056.aspx. When a user attempts to join a conferencing session or begin application sharing, the Lync Server Audio/Video Conferencing service or Lync Server Application Sharing service, performs a bandwidth check before the media traffic connection is established. If there is sufficient bandwidth, the media traffic is allowed; otherwise, the Audio/Video Conferencing service blocks it. In the case of application sharing, traffic is always allowed and bandwidth checks always succeed.
Figure 3 shows the scenario where a PSTN gateway user joins a conference.
Figure 3. CAC and Lync Server 2010 A/V Conferencing Server
Here’s what occurs:
promagna1