Topic Last Modified: 2011-01-26

Microsoft Lync Server 2010 voice policies define the following for each user, site, or organization that is assigned the policy:

Planning for Voice Policies

To plan the voice policies you will need for your Enterprise Voice deployment:

  • Determine how you will configure your default Global voice policy. This policy will apply to all Enterprise Voice users who are not explicitly assigned a site-level or per-user policy.

  • Identify any site-level voice policies you might need.

  • Identify any per-user voice policies you might need.

  • Decide which call features to enable for each voice policy.

  • Determine what PSTN usage records to configure for each voice policy.

Voice Policy Scope

Voice policy scope determines the hierarchical level at which the policy can be applied. In Lync Server 2010, you can configure voice policies with the following scope levels (listed from the most specific to the most general).

  • User voice policy can be assigned to individual users, groups, or contact objects. This is the lowest level policy. User voice policies can be deployed to enable features for certain users or groups at a site, but not for others in the same site. For example, you may want to disable long distance dialing for some employees. For the purpose of assigning a voice policy, a Contact object is treated as an individual user.

    We recommend that for branch site Enterprise Voice users who are registered with the central site deployment or users who are registered on a Survivable Branch Appliance you deploy a user voice policy.
  • Site voice policy applies to an entire site, except for any users, groups, or contact objects that are assigned a User voice policy. To define a Site voice policy, you must specify the site to which the policy applies. If a User voice policy is not assigned, the Site voice policy is used.

  • Global voice policy is the default voice policy that is installed with the product. You can edit the Global voice policy to meet the specific needs of your organization, but you cannot rename or delete it. This voice policy applies to all Enterprise Voice users, groups, and contact objects in your deployment unless you configure and assign a voice policy with more specific scope. If you want to disable this policy entirely, ensure that all sites and users have custom policies assigned to them.

Call Features

You can enable or disable the following call features for each voice policy:

  • Call forwarding enables users to forward calls to other phones and client devices. Enabled by default.

  • Delegation enables users to specify other users to send and receive calls on their behalf. Enabled by default.

  • Call transfer enables users to transfer calls to other users. Enabled by default.

  • Call park enables users to park calls and then pick up the call from a different phone or client. Disabled by default.

  • Simultaneous ringing enables incoming calls to ring on an additional phone (for example, a mobile phone) or other endpoint devices. Enabled by default.

  • Team call enables users on a defined team to answer calls for other members of the team. Enabled by default.

  • PSTN reroute enables calls made by users who are assigned this policy to other enterprise users to be rerouted on the public switched telephone network (PSTN) if the WAN is congested or unavailable. Enabled by default.

  • Bandwidth policy override enables administrators to override call admission control policy decisions for a particular user. Disabled by default.

  • Malicious call tracing enables users to report malicious calls by using the Microsoft Lync 2010 client, and then flags such calls in the call detail records. Disabled by default.

PSTN Usage Records

Each voice policy should have one or more associated PSTN usage records. For details about planning PSTN usage records, see PSTN Usage Records.

PSTN usage order is critical because in matching users to routes, the outbound routing functionality compares PSTN usages from top to bottom. If the first usage matches the call route, that route is used. If not, the outbound routing functionality looks at the next PSTN usage on the list and continues until a match is found. In effect, the subsequent PSTN usages provide backup if the first one on the list is unavailable.