7. Translation Rules
Translation
rules are a powerful new feature in Lync Server 2010 that enables digit
manipulation to a PBX or media gateway. Lync Server recommends all
numbers be the E.164 format, but a PBX or gateway might be configured
for local dialing or require special access codes before accepting dial
strings.
With translation rules on a trunk, an administrator
can configure Lync Server to modify the dial string before sending it
to the trunk. This ability is not available in Office Communications
Server. For example, the translation rules can now remove a prefix such
as +44 and replace it with 901144 before sending the string to the PBX.
Administrators can either define the translation rules using regular
expressions or using the Translation Rule tool.
To create a new translation rule, complete the following steps:
1. | On the Edit Trunk Configuration screen, click the New button in the Associated Translation Rules section.
|
2. | Provide a Name and a Description for the rule.
Note
This example uses the Translation Rule tool, but for
more advanced pattern matching, click the Edit button at the bottom of
the screen to manually enter the matching pattern and translation rule
using regular expressions.
|
3. | In the Starting digits field, enter the beginning digits of the string to be matched.
|
4. | Specify a Length
of the string to be matched. Options include matching at least a
specific number of digits, exactly a certain number of digits or any
number of digits.
|
5. | Specify a number of Digits to remove after a string matches the starting digits and length.
|
6. | Specify Digits to add after the selected number of digits have been removed.
|
7. | Click OK to save the translation rule and click OK again to save the trunk configuration.
|
8. Export and Import Voice Configuration
Lync Server 2010 enables administrators to easily
export and import the entire voice-routing configuration from a system.
To export a configuration, use the following steps:
1. | Open the Lync Server 2010 Control Panel.
|
2. | Click Voice Routing.
|
3. | From any of the submenu selections, click Actions, and then click Export configuration.
|
4. | Select a location to save the configuration file, and then click Save. The file format has a VCFG extension.
|
To import a previously saved configuration file, use the following steps:
1. | Open the Lync Server 2010 Control Panel.
|
2. | Click Voice Routing.
|
3. | From any of the submenu selections, click Actions and then click Import configuration.
|
4. | Locate the configuration file and click Open.
|
Note
Like all other voice configuration changes, an imported configuration won’t be active until published.
9. Test Cases
Test cases enable administrators to verify the voice
configuration works as expected. To create a new voice routing test
case, use the following steps:
1. | Open the Lync Server 2010 Control Panel.
|
2. | Click Voice Routing.
|
3. | Click Test Voice Routing.
|
4. | Click the New button to create a new test case.
|
5. | Enter a Name for the case.
|
6. | Enter a Dialed number
to test. This is the number a user enters into the Lync client and is
normalized based on the selection dial plan selected next.
|
7. | Select a Dial Plan.
|
8. | Select a Voice policy.
|
9. | Enter an Expected translation.
This is the string the dialed number to test string is expected to be
translated to. If a normalization rule in the dial plan does not
convert the dialed number to this string, the test is recorded as a
failure.
|
10. | Select an Expected PSTN usage
for the test case. This field is optional. If the test case matches a
PSTN usage other than the one selected here, the test is recorded as a
failure.
|
11. | Select an Expected route
for the test case. This field is optional. If the voice test matches a
route other than the one selected here, the test is recorded as a
failure.
|
12. | Click the Run button to begin the test.
|
13. | To save the test case, click the OK button. Figure 2
shows a sample test case that has failed all tests. This indicates an
administrator should modify the voice configuration before publishing
the changes.
|
