Topic Last Modified: 2010-12-12
This topic explains how to edit a voice route. To create a new route, see Create a Voice Route.
To modify a voice route
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.
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.
In the left navigation bar, click Voice Routing and then click Route.
On the Route page, use either of the following methods to modify a voice route:
- Click a voice route name, click Edit, and then click
- Click a voice route name, click Edit, click Copy,
and then click Paste. Click the new copy of the voice route
that you just created, click Edit, and then click Show
- Click a voice route name, click Edit, and then click Show details.
In the Name field on the Edit Voice Route page, type a descriptive name for the voice route.
(Optional) In the Description field, type in additional descriptive information for the voice route.
To specify the patterns 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.
- 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.
- 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
information about how to write regular expressions, see ".NET
Framework Regular Expressions" at http://go.microsoft.com/fwlink/?LinkId=140927.
- 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:
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.
To associate one or more PSTN gateways or SIP trunks with the voice route, click Add and then select a gateway or SIP trunk from the list.
Note: If your deployment includes any Microsoft Office Communications Server 2007 R2 Mediation Servers, they will also be available in the list.
To associate one or more PSTN usage records 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.
Note: 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.
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: Unlike in a voice policy where the order in which PSTN usage records are listed is important, the order in a 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.)
(Optional) Type a value into the Enter a translated number to test field and click Go. The test results are displayed under the field.
Note: You can save a voice route that does not yet pass the test and then reconfigure it later. For details, see Test Voice Routing.
On the Route page, click Commit, and then click Commit all.
Note: Any time you create or modify 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 in the Operations documentation.