Defining Translation Rules
Topic Last Modified: 2012-10-14
Microsoft Lync Server 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.
Important
The ability to associate one or more translation rules with an Enterprise Voice trunk configuration is intended to be used as an alternative to configuring translation rules on the trunk peer. Do not associate translation rules with an Enterprise Voice trunk configuration if you have configured translation rules on the trunk peer because the two rules might conflict.
You can use either of the following methods to create or modify a translation rule:
Use the Build a Translation Rule tool to specify values for the starting digits, length, digits to remove and digits to add, and then let Lync Server Control Panel generate the corresponding matching pattern and translation rule for you.
Write regular expressions manually to define the matching pattern and translation rule.
Note
For information about how to write regular expressions, see ".NET Framework Regular Expressions" at https://go.microsoft.com/fwlink/p/?LinkId=140927.
In This Section