[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-16

Voice policies, PSTN usage records, and voice routes are integrally related.

You configure voice policies by selecting a set of calling features and then assigning the policy a set of PSTN usage records, which specify what permissions are authorized for the users or groups who are assigned the voice policy.

Voice routes are also assigned PSTN usage records, which serve to match routes with the users who are authorized to use them. That is, users can only place calls that use the routes for which they have a matching PSTN usage record.

The recommended workflow for a new Enterprise Voice deployment is to start by configuring a voice policy that includes the appropriate PSTN usage records, and then associate the appropriate routes to each PSTN usage record. For example, if you want to create a voice policy that applies to all users at a Redmond central site named co1, the Communications Server Control Panel workflow is as follows:

  1. Create a site voice policy named co1 and enter “Redmond Central Site” in the Description field.

  2. Enable the calling features you want to assign to the users who will be assigned this policy.

  3. While you are configuring the co1 voice policy on the New Voice Policy dialog box, associate the necessary PSTN usage records (for example Internal, Local, and Long Distance). If necessary, create any additional PSTN usage records the co1 site might need.

  4. Associate the appropriate routes to each PSTN usage record you have included in the voice policy. For example, associate the LocalRoute voice route with the Local PSTN usage record. If necessary, create any additional routes for the assigned PSTN usage records.

  5. Save the co1 voice policy.

  6. Run the Commit All command to commit the co1 voice policy (and any other pending changes) to the database.

You can also create voice policies with user scope and assign them to individual users or groups.

For the detailed steps to perform each of these tasks, see the procedures in this section.

In This Section