Use the Add Location Profile or Edit Location Profile dialog boxes to create or modify a location profile.
Type a clear, descriptive name for the location profile. This 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: ) or (. No other special characters including spaces are allowed. The name typically reflects the location to which it applies. If you are integrating Exchange Unified Messaging (UM) with Office Communications Server, the name of the location profile must match the fully qualified domain name (FQDN) of the corresponding UM dial plan.
It is recommended, but not required, that you type the common, recognizable name of the geographic location to which the corresponding location profile applies. For example, if the location profile name is London.Contoso.com, then the recommended Display text would be London. If you have deployed Office Communicator Phone Edition, the name in this field will be displayed to end users for the purpose of allowing them to select the appropriate location profile for a call. If you have deployed dial-in conferencing, this name is used to configure a region in the Conferencing Attendant application properties. The region that you configure for Conferencing Attendant is then displayed alongside each conference access number in the meeting options for meeting invitations and on the Dial-in Conferencing Settings Web page for users.
Optimize device dialing
If you want to add an external access prefix, select this check box, which activates the External access prefix text box.
External access prefix
This box becomes active when you select the Optimize device dialing check box. You can specify an external access prefix that, for example, matches a long distance prefix, by typing up to four characters (#, *, and 0-9) in this box.
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.
To add a normalization rule, click Add.
To revise a normalization rule, click the rule in the list, and then click Edit.
To delete a normalization rule, click the rule in the list, and then click Remove.
To move a normalization rule up in the list, click the rule in the list, and then click Up.
To move a normalization rule down in the list, click the rule in the list, and then click Down.
Important: The order of normalization rules is significant because, when attempting to match dialed numbers, the server applies the list from top to bottom. 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. For details about routing logic, as well as routing samples, see Enterprise Voice documentation in the Office Communications Server Technical Library.
Learn More Online
Click to expand or collapse
A normalization rule specifies how to convert dialed numbers in various formats to the standard E.164 format for purposes of reverse number lookup. 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. You must specify a new and unique name for the new normalization rule. If required, you can also modify any of the copied settings, as appropriate to the location.
To create Exchange UM dial plans, you can use the OcsUMUtil tool that is included with Office Communications Server 2007 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, see the Office Communications Server Technical Library.