Normalization Rules

,

Normalization rules are what dial plans use to take a user’s extension and translate it to a full E.164 format that can be matched to a user account. Continuing from the dial plan creation screen, perform the following steps to create a normalization rule:

1. On the Edit Dial Plan screen, click the New button in the Associated Normalization Rules section.

2. Provide a Name for the rule and Description for the rule.

Note

This example uses the Normalization Rule tool. 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 are removed.

7. If the pattern matches numbers that are internal to the organization, check the Internal extension box.

8. Click OK to save the translation rule, and then click OK again to save the trunk configuration.

For example, assume an organization uses four-digit dialing from a specific site. All direct inward dial (DID) numbers within that site start with 234–567, followed by the four-digit extension. In this scenario, the pattern and translation rule are configured as in the following:

Pattern to match: ^(d{4})$
Translation rule: +1234567$1

This takes a four-digit extension and prepends +1234567 in front of the four digits. Assuming a user has the 1234 extension and a user account was assigned a Tel URI of tel:+12345671234, the conferencing service matches the user account based on this rule.

Caution

It might be necessary to include a number of normalization rules in the dial plan in case blocks of DID numbers are noncontiguous. In a worst-case scenario, the DIDs do not follow a repeatable pattern when matched to extensions and many rules might need to be created.

When creating multiple rules, be sure to order them in a top-to-bottom format because Lync uses the first rule that it matches. Keep this in mind when troubleshooting why a normalization rule is not translating correctly.

One way to mitigate these kinds of errors is to test the pattern immediately. When creating a new rule, simply enter a dial string in the Phone number to test field and a success or failure will be returned immediately. If the test succeeds, be sure the normalized number is correct because the test only indicates a failure or success at matching the original pattern.

Note

One common question organizations have is how to enable dial-in conferencing for users without a DID. In these cases, use a main office or front desk number as the Tel URI, but append an ;ext=xxxx string to the end of the Tel URI. Using the previous example, assume the user’s extension is still 1234, but the main office number is 234-567-8000. The user’s Tel URI would be tel:+1234567890;ext=1234.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset