Topic Last Modified: 2012-11-01

The following procedure explains how to create a new voice route by using the Lync Server 2013 Control Panel. To edit an existing route, see Modify a Voice Route for the procedure.

To create a voice route by using the Lync Server Control Panel

  1. Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, or CsAdministrator administrative role.

  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.

  4. Click Route.

  5. Click New to display the New Voice Route dialog box.

  6. In Name, type a descriptive name for the voice route.

  7. (Optional) In Description, type additional descriptive information for the voice route.

  8. To specify the patterns that you want this route to accommodate, you can either use the Build a pattern to match tool to generate a regular expression, or write the regular expression manually.

    • To use the Build a pattern to match tool to generate a regular expression, enter values as follows. You can specify two types of pattern matching:

      • Starting digits for numbers that you want to allow: Enter prefix values that this route must accommodate (including the leading + if needed). For example, type +425, and then click Add. Repeat this for each prefix value that you want to include in the route.

      • Exceptions: If you want to specify one or more exceptions for a prefix value, highlight the prefix and click Exceptions. Type in one or more values for the matching patterns that you do not want this route to accommodate. For example, to exclude numbers starting with +425237 from the route, enter a value of +425237 in the Exceptions field, and then click OK.

    • To define the matching pattern manually, click Edit in the Build a pattern to match tool and then type in a .NET Framework regular expression to specify the matching pattern for destination phone numbers to which the route is applied. For details about how to write regular expressions, see ".NET Framework Regular Expressions" at

  9. Select Suppress caller ID if you do not want the ID of the phone making the outbound call to appear to the call recipient. If you select this option, you must specify an Alternate caller ID that will appear on the recipient’s caller ID display.

  10. To associate one or more trunks with the voice route, click Add and then select a trunk from the list.

    If your deployment includes any Microsoft Office Communications Server 2007 R2 Mediation Servers, they will also be available in the list.
  11. To associate one or more public switched telephone network (PSTN) usages with the voice route, click Select and choose a record from the list of PSTN usage records that have been defined for your Enterprise Voice deployment.

    To view the properties of each of the available PSTN usage records, see View PSTN Usage Records.

    To create or edit PSTN usage records, see Create a Voice Policy and Configure PSTN Usage Records or Modify a Voice Policy and Configure PSTN Usage Records.
  12. 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.

    In contrast to a voice policy, where the order in which PSTN usage records are listed is important, the order in which PSTN usage records are listed in the voice route is insignificant. However, we recommend that you organize the list by frequency of use. For example: RedmondLocal, RedmondLongDist, RedmondInternational, RedmondBackup. (Lync Server traverses the list from the top down.)
  13. (Optional) Type a value into the Enter a translated number to test field and click Go. The test results are displayed under the field.

    You can save a voice route that does not yet pass the test and then reconfigure it later. For details, see Test Voice Routing.
  14. Click OK to save the voice route.

Whenever you create a voice route, you must run the Commit All command to publish the configuration change. For details, see Publish Pending Changes to the Voice Routing Configuration.

See Also