Creating and Configuring Location Profiles

A location profile is a named set of normalization rules that translate phone numbers for a named location to a single standard (E.164) format for purposes of phone authorization and call routing. Beginning with Office Communications Server 2007 R2, location profiles can also be assigned to individual users. The same phone number dialed from different locations can resolve to different E.164 numbers, depending on the assigned location profile. Similarly, the same phone number dialed from the same location can resolve to different E.164 numbers if the numbers are dialed by users to whom different location profiles have been assigned.

In Office Communications Server 2007 R2:

You can assign location profiles for individual users.
Enterprise Voice applications can look up and use a per-user location profile when a phone-context value of user-defaultis received.
Location profiles can be assigned to Contact objects in addition to individual users.
In-band provisioning can be used to send a per-user location profile to the user. If a per-user location profile is not assigned to the user, in-band provisioning sends the pool-level default location profile.
You can optimize device dialing by adding an external access prefix of up to four characters (#, *, and 0-9).

Creating and configuring location profiles includes specifying the following:

Name. The name that you assign to the location profile typically reflects the location to which it applies. If integrating Exchange Unified Messaging (UM) with Office Communications Server, the name of the location profile must match the FQDN of the corresponding UM dial plan. The name must be unique and cannot exceed 256 Unicode characters, each of which can be an alphabetic or numeric character, a hyphen, a dot, a plus sign, an underscore, or either a left or right parenthesis. No other special characters, including spaces, are allowed.
Display text. The display text describes the location profile in more detail. It should be recognizable and significant to end users who might encounter it.
Optimize device dialing. You can add an external access prefix by selecting the Optimize device dialingcheck box, and then, in the External access prefixtext entry box, typing up to four characters (#, *, and 0-9).
Normalization Rules. This list contains all the normalization rules that have been defined and that, therefore, are available for this location profile. Each location profile must have at least one normalization rule. The normalization rules define how phone numbers expressed in various formats are to be routed for the named location by specifying how to convert dialed numbers in various formats to the standard E.164 format for purposes of reverse number lookup. The same number string can be interpreted and translated differently depending on the locale from which it is dialed. Normalizing user-supplied phone numbers provides a consistent format that makes it possible to match a dialed number to the intended recipient's SIP-URI and to apply dialing authorization rules to the calling party.

You cannot assign a single phone number normalization rule to multiple location profiles. Instead, you create a separate normalization rule for each location profile. To facilitate the process of specifying each normalization rule, you can copy an existing normalization rule. When you copy a normalization rule, the existing rule is used as a template for the creation of the new normalization rule.

The order of normalization rules is significant because the server applies the list from top to bottom when it attempts to match dialed numbers to rules. If the first rule matches the dialed number, the server quits looking and proceeds with routing. Typically, to expedite routing, put the normalization rules in order, starting with the most general rule at the top of the list and going to the most specific rule at the bottom of the list.

A large organization may need a separate location profile for each location where it maintains an office. If your organization has a legacy PBX deployed, you can use its dial plan to create location profiles.

Note:
If you intend to configure Exchange Server 2007 UM to work with Enterprise Voice, we recommend that you do that before you create the location profiles. Each Exchange UM dial plan requires a corresponding location profile. If you use the same dial plan name in multiple Exchange forests, you must create a matching location profile specific to the UM dial plan FQDN for each forest. After creating location profiles, you must configure Office Communications Server to work with Exchange UM, as well as complete deployment and configuration of other components. To create Exchange UM dial plans, you can use the OcsUMUtil tool, which is included with Office Communications Server 2007 R2, to validate the names of the corresponding location profiles. The tool does not correct invalid names, but it does identify each location profile name that does not match the FQDN of the corresponding UM dial plan. For details about the use of this tool and other planning and implementation information, see Step 3. Configure Communications Server to Work with Unified Messaging on Microsoft Exchange Serverin the Deploying Enterprise Voice documentation.

Note:

If you intend to configure Exchange Server 2007 UM to work with Enterprise Voice, we recommend that you do that before you create the location profiles. Each Exchange UM dial plan requires a corresponding location profile. If you use the same dial plan name in multiple Exchange forests, you must create a matching location profile specific to the UM dial plan FQDN for each forest. After creating location profiles, you must configure Office Communications Server to work with Exchange UM, as well as complete deployment and configuration of other components.

To create Exchange UM dial plans, you can use the OcsUMUtil tool, which is included with Office Communications Server 2007 R2, to validate the names of the corresponding location profiles. The tool does not correct invalid names, but it does identify each location profile name that does not match the FQDN of the corresponding UM dial plan. For details about the use of this tool and other planning and implementation information, see Step 3. Configure Communications Server to Work with Unified Messaging on Microsoft Exchange Serverin the Deploying Enterprise Voice documentation.

After creating location profiles for an Office Communications Server 2007 R2 Enterprise pool, you need to assign a default location profile for each Office Communications Server Front End Server pool, and Mediation Server (or Advanced Media Gateway). The Front End Server and pool use the translated number that is obtained by applying the normalization rules to determine the media gateways to which calls to the PSTN or a PBX are to be routed. The Mediation Server receives E.164 numbers from the gateway, uses the location profile to determine how to interpret the E.164 number for local dialing, and then routes the number to the next hop server for reverse lookup. You must configure the PSTN gateway to convert telephone numbers from a national format to the E.164 format before sending them to the Mediation Server.

For details about location profiles and how they are used, including routing logic, see Location Profilesin the Planning and Architecture documentation.

To create or configure a location profile

Open the Office Communications Server 2007 snap-in.
In the console pane, right-click the Forestnode, point to Properties, and click Voice Properties.
On the Location Profilestab, click Addto create new location profiles, or click Editto edit existing profiles.

In the Namebox, type a useful descriptive name.

Important:
If you are planning to configure Exchange Server Unified Messaging for Enterprise Voice but have not yet done so, configure it now. For details, see Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Serverin the Deploying Enterprise Voice documentation.

Note:
If you have configured Exchange Unified Messaging for Enterprise Voice and have completed Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Serverin the Deploying Enterprise Voice documentation, type the fully qualified domain name (FQDN) of the corresponding Exchange Unified Messaging dial plan.

Note:
This name must be unique and cannot exceed 256 Unicode characters, each of which can be an alphabetic or numeric character, a hyphen (-), a period (.), a plus sign (+), an underscore ( _ ), or either left or right parenthesis: ) or (.

In the Descriptionbox, type the common, recognizable name of the geographic location to which the location profile applies.

Note:
For example, if the location profile name is London.Contoso.com, the recommended Descriptionis London. If you have deployed Conferencing Attendant, this description is included as part of the region information in the conferencing e-mail invitation.

If you want to add an external access prefix, select the Optimize device dialingcheck box, and then in the External access prefixtext entry box, when it becomes active, type up to four characters (#, *, and 0-9) in this box.
Click Addto open the Add Phone Number Normalization Ruledialog box, or Editto open the Edit Phone Number Normalization Ruledialog box.
In the Namebox, type a name that describes the number pattern being normalized (for example, 5DigitExtensionor 7 digit calling Toronto).
Do one of the following:
- If you want to create a new normalization rule, skip this step and the following step.
- If you want to copy the phone pattern and translation pattern of an existing normalization rule, click Copy rule.
In the Copy Phone Number Normalization Ruledialog box, select the normalization rule that you want to copy, and then click OK.

Note:

If you want to view a normalization rule before copying it, select the rule, and then click View.
In the Descriptionbox, type a brief description of the normalization rule (for example, "Translates 5-digit extensions" or "Translates 7-digit numbers to Toronto local number").
In the Phone pattern regular expressionbox, use .NET Framework regular expressions to describe a phone number pattern (for example, ^9(\d{7})$, which describes a phone number pattern consisting of the number 9 followed by any seven digits).

Note:

For details about using .NET Framework regular expressions, see the.NET Framework Regular Expressions Web site at http://go.microsoft.com/fwlink/?LinkId=140927 .
In the Translation pattern regular expressionbox, use .NET Framework regular expressions to describe the E.164 phone number corresponding to the number entered in the Phone pattern regular expressionbox.
If the normalization rule results in a phone number that is internal to the enterprise, click Internal enterprise extension.
If you do not want the rule to be applied when dialing from a device, clear Use translation when dialing from device.
If you require assistance in formulating regular expressions for phone number normalization rules, click Launch guide.
In the Sample dialed numberbox, type a phone number to test whether the number translation works properly.

Note:

If the number matches the phone pattern, the translation is shown in the Translated numberbox.
If the translation matches the phone pattern, click OK.
When you are done, click OK.

To create or configure a location profile

See Also

Other Resources