Add or Edit Enterprise Voice Policy

Use the Add Policy dialog box to define a new policy for Enterprise Voice. Use the Edit Policy dialog box to edit an existing policy for Enterprise Voice.

Policy name

Type a clear, descriptive name for the policy. The name can be up to 256 Unicode characters.

Allow simultaneous ringing of phones

To provide the user with the option of designating an additional phone (for example, a mobile phone) that rings at the same time as the user's primary phone (that is, a registered SIP endpoint), select this check box. To enable only ringing of the primary phone, clear the check box

Phone usages

This list contains the phone usage records that are assigned to this policy. To add or remove phone usage records from the list, click Configure.

Learn More Online

Click to expand or collapse

The name of each Enterprise Voice policy should make it easy to identify the collection of phone usage records it contains and its purpose. For example, RedmondUsers.

The simultaneous ringing feature enables each user to configure Office Communicator such that incoming calls, in addition to ringing the user's registered endpoints, also ring an additional non-registered endpoint, such as a personal mobile phone. Normally, simultaneous ringing should be enabled, but in the event of excessive congestion, you can disable this feature.

A phone usage record is a named class of calls (for example, local, long-distance, or international). To implement call authorizations, phone usage records are first defined, and then assigned both to the policy (that is, by using this dialog box) and to routes. To define a phone usage record, use the Phone Usages tab of Voice Properties. To assign a phone usage record to a route, use the Routes tab of Voice Properties.

For details about Enterprise Voice policies and phone usage records on the Web, see the Office Communications Server Technical Library.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×