Symptoms

Consider the following scenario:

  • You deploy Enterprise Voice in a Microsoft Lync Server 2010 environment.

  • You create a telephone number normalization rule. The pattern of this rule includes a prefix that contains optional digits, such as a question mark (?) or an asterisk (*). For example, you set the Pattern to match field to ^(1)?([2-9]\d\d[2-9]\d{6})$ and the Translation rule field to +1$2. This rule changes the telephone numbers 1XXXXXXXXXX and XXXXXXXXXX to +1XXXXXXXXXX.

  • A user in the environment makes a call to a telephone number by using a client that does not support client-side normalization. For example, the user uses the Unified Messaging Play on Phone feature in Microsoft Exchange or a Public Switched Telephone Network (PSTN) telephone.

  • The telephone number matches the pattern but does not contain the prefix. For example, the user dials XXXXXXXXXX.

In this scenario, the user cannot make the call.

Cause

This issue occurs because the prefix matching optimization that Lync Server 2010 uses to change telephone numbers cannot handle expressions that begin with optional digits.

Resolution

To resolve this issue, install the following cumulative update:

2670352 Description of the cumulative update for Lync Server 2010: February 2012

Workaround

To work around the issue, use two rules instead of one. One rule should contain the prefix, and the other rule should not contain the prefix. 

For example, you can use the following two rules instead of the rule that is described in the "Symptoms" section:

  • In the first rule, set the Pattern to match field to ^1([2-9]\d\d[2-9]\d{6})$ and set the Translation rule field to +1$1.

  • In the second rule, set the Pattern to match field to ^([2-9]\d\d[2-9]\d{6})$ and set the Translation rule field to +1$1.

More Information

For more information about the telephone normalization rules, visit the following Microsoft website:

General information about the telephone normalization rulesFor more information about the telephone number normalization rule regular expressions, visit the following Microsoft website:

General information about the telephone number normalization rule regular expressionsFor more information about how to define translation rules, visit the following Microsoft website:

How to define translation rulesFor more information about how to create or modify a translation rule manually, visit the following Microsoft website:

How to create or modify a translation rule manually

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×