Topic Last Modified: 2012-08-06
Follow these steps if you want to define a translation rule by writing a regular expression for the matching pattern and translation rule. Alternatively, you can enter a set of values in the Build a Translation Rule tool and enable Lync Server Control Panel to generate the corresponding matching pattern and translation rule for you. For details, see Create or Modify a Translation Rule by Using the Build a Translation Rule Tool.
To define a translation rule manually
-
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.
-
To begin defining a translation rule, follow the steps in Configure a Trunk with Media Bypass through step 10 or Configure a Trunk without Media Bypass through step 9.
-
In the Name field on the New Translation Rule or Edit Translation Rule page, type a name that describes the number pattern being translated.
-
(Optional) In Description, type a description of the translation rule, for example US International long-distance dialing.
-
Click Edit at the bottom of the Build a Translation Rule section.
-
Enter the following in Type a Regular Expression:
-
In Match this pattern, specify the pattern that will be used to match the numbers to be translated.
-
In Translation rule, specify a pattern for the format of translated numbers.
For example, if you enter ^\+(\d{9}\d+)$ in Match this pattern and 011$1 in Translation rule, the rule will translate +441235551010 to 011441235551010.
-
-
Click OK to save the translation rule.
-
Click OK to save the trunk configuration.
-
On the Trunk Configuration page, click Commit, and then click Commit all.
Note: Whenever you create or modify a translation rule, 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.