1. Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, or CsAdministrator role. For details, see Delegate Setup Permissions.

2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

3. In the left navigation bar, click Voice Routing and then click Voice Policy.

4. On the Voice Policy page, double-click a voice policy name.

   Note:
   The scope and name were set when the voice policy was created. They cannot be changed.

5. (Optional) In Edit Voice Policy, enter additional descriptive information for the voice policy.

6. Select or clear the following check boxes to enable or disable each of the Calling features:

   • 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 on hold and then pick up the call from a different phone or client. Disabled by default.
     
     
   • Simultaneous ringing enables incoming calls to ring on additional phones (for example, a cell 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 re-route enables calls made by users who are assigned this policy to other enterprise users to be re-routed 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 (CAC) policy decisions for a particular user. Disabled by default.
     
     

     Note:
     The policy will be overridden only for incoming calls to the user and not for outgoing calls that are placed by the user. After the session is established the bandwidth consumption will be accurately accounted for. This setting should be used sparingly and should be avoided for appropriate call admission control decisions.

   • Malicious call tracing enables users to report malicious calls (such as bomb threats) using the client UI, and that in turn flags the calls in the call detail records (CDRs). Disabled by default.
     
     

7. To associate and configure PSTN usage records for this voice policy, do any of the following:

   • To choose one or more records from a list of all PSTN usage records available in your Enterprise Voice deployment, click Select. Highlight the records you want to associate with this voice policy and then click OK.
     
     
   • To remove a PSTN usage record from this voice policy, highlight the record and click Remove.
     
     
   • To define a new PSTN usage record and associate it with this voice policy, do the following:
     
     
     1. Click New.
        
        
     2. In the Name field, enter a unique descriptive name for the record. For example, you may want to create a PSTN usage record named Redmond for full-time employees located in Redmond, and another named RedmondTemps for temporary employees.
        
        

        Note:
        The PSTN usage record name must be unique within the Enterprise Voice deployment. After the record is saved, the Name field cannot be edited.

     3. Use any of the following methods to associate and configure routes for this PSTN usage record:
        
        
        • To choose one or more routes from the list of all available routes in your Enterprise Voice deployment, click Select, highlight the routes you want to associate with this PSTN usage record, and then click OK.
          
          
        • To remove a route from the PSTN usage record, highlight the route and click Remove.
          
          
        • To define a new route and associate it with this PSTN usage record, click New. For details, see Create a Voice Route.
          
          
        • To edit a route that is already associated with this PSTN usage record, highlight the route and click Show details. For details, see Modify a Voice Route.
          
          
     4. Click OK.
        
        
   • To edit a PSTN usage record that is already associated with this voice policy, do the following:
     
     
     1. Highlight the PSTN usage record you want to edit and click Show details.
        
        
     2. Use any of the following methods to associate and configure routes for this PSTN usage record:
        
        
        • To choose one or more routes from the list of all available routes in your Enterprise Voice deployment, click Select, highlight the routes you want to associate with this PSTN usage record, and then click OK.
          
          
        • To remove a route from this PSTN usage record, highlight the route and click Remove.
          
          
        • To define a new route and associate it with this PSTN usage record, click New. For details, see Create a Voice Route.
          
          
        • To edit a route that is already associated with this PSTN usage record, highlight the route and click Show details. For details, see Modify a Voice Route.
          
          
     3. Click OK.
        
        

8. Arrange the PSTN usage records for optimum performance. To change a record’s position in the list, highlight the record name and click the up or down arrow.

   Note:
   The order in which PSTN usage records are listed in the voice policy is significant. Lync Server traverses the list from the top down. We recommend that you organize the list by frequency of use, for example: RedmondLocal, RedmondLongDist, RedmondInternational, RedmondBackup.

9. (Optional) Enter a number to test the voice policy and click Go. The test results are displayed below the Translated number to test field.

   Note:
   You can save a voice policy that does not yet pass the test and then reconfigure it later. For details, see Test Voice Routing.

10. Click OK.

11. On the Voice Policy page, click Commit, and then click Commit all.

    Note:
    Any time you create or modify a voice policy, you must run the Commit all command to publish the configuration change. For details, see Publish Pending Changes to the Voice Routing Configuration in the Operations documentation.

Tasks

Other Resources