Lync 2010 Translation Rules



MSLync 2010 Enterprise Voice requires that all dial strings be normalized to E.164 format for the purpose of performing reverse number lookup (RNL). The trunk peer (that is, the associated gateway, PBX, or SIP trunk) might require that numbers be in a local dialing format. To translate numbers from E.164 format to a local dialing format, you can optionally define one or more translation rules to manipulate the Request URI before routing it to the trunk peer. For example, you could write a translation rule to remove +44 from the beginning of a dial string and replace it with 0144.

 

Use either of the following methods to create or modify a translation rule:



The Build a Translation Rule Tool
Follow the steps if you want to define a translation rule by entering a set of values in the Build a Translation Rule tool and allowing Lync Server Control Panel to generate the corresponding matching pattern and translation rule for you. Alternatively, you can a write regular expression manually to define the matching pattern and translation rule.

To define a rule by using the Build a Translation Rule tool:

  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 Name field on the New Translation Rule or Edit Translation Rule page, type a name that describes the number pattern being translated.
  4. (Optional) In Description field, type a description of the translation rule, for example US International long-distance dialing.
  5. In the Build a Translation Rule section of the dialog box, enter values in the following fields:
    • Starting digits: (Optional) Specify the leading digits of numbers you want the pattern to match. For example, enter + in this field to match numbers in E.164 format (which begin with +).
    • Length: Specify the number of digits in the matching pattern and select whether you want the pattern to match numbers that are this length exactly, at least this length, or any length. For example, enter 11 and select At least in the drop-down list to match numbers that are at least 11 digits in length.
    • Digits to remove: (Optional) Specify the number of starting digits to be removed. For example, enter 1 to strip out the + from the beginning of the number.
    • Digits to add: (Optional) Specify digits to be prepended to the translated numbers. For example, enter 011 if you want 011 to be prepended to the translated numbers when the rule is applied.

      The values you enter in these fields are reflected in the Pattern to match and Translation rule fields. For example, if you specify the preceding example values, the resulting regular expression in the Pattern to match field is:

    ^\+(\d{9}\d+)$

    The Translation rule field specifies a pattern for the format of translated numbers. This pattern has two parts:

      • A value (for example, $1) that represents the number of digits in the matching pattern.
      • (Optional) A value that you can prepend by entering it in the Digits to add field

    Using the preceding example values, 011$1 appears in the Translation rule field.

    When this translation rule is applied, +441235551010 becomes 011441235551010.

  6. Click OK to save the translation rule.
  7. Click OK to save the trunk configuration.
  8. On the Trunk Configuration page, click Commit, and then click Commit all.