Sites Dialog Box

This topic describes how to use the Sites dialog box to configure sites and site groups for the voice mail domain. You can also configure the maximum call costs and enable the MultiSite feature on this dialog box.


Notes: For more information on the MultiSite feature and the concepts underlying MultiSite, such as sites and translation rules, see the Avaya Modular Messaging MultiSite Guide. When a new VMD is created, an option allows it to be enabled for MultiSite. The option is not enabled by default. Enabling MultiSite requires careful planning, because when you disable MultiSite, you must configure the site-level settings again to apply to the entire voice mail domain. You must also reconfigure the mailbox length for the voice mail domain. You can configure sites and site groups for a voice mail domain regardless of whether MultiSite is enabled. However, the configurations will take effect only after MultiSite is enabled. MultiSite can only be enabled if all MASs in the voice mail domain have Avaya Modular Messaging Release 5.0 software installed. MultiSite can only be enabled if all MASs in the voice mail domain are running and available. All MASs in the voice mail domain must use SIP-based IP integration to communicate with the PBX. In a MultiSite-enabled VMD, you can only add SIP PBXs to a voice mail domain. See PBX Configuration - SIP Tab (IP SIP) and PBX Integration Dialog Box. Once created, you cannot change the identifier of a site or site-group. See Sites - Site Configuration Dialog Box.

Launching the Screen

In the Voice Mail System Configuration window, click the voice mail domain (VMD).

Double-click Sites. The system displays the Sites dialog box for the selected voice mail domain.

Configuring the Screen Controls

Enable MultiSite Select this option to enable MultiSite for the voice mail domain. In case of a new installation of Avaya Modular Messaging Release 5.0, this checkbox is selected if MultiSite is enabled when creating a *.mmdct file using the Data Collection Tool (DCT).

Costs controlling outbound calls In a MultiSite-enabled environment, a cost is associated with all outgoing calls. The associated cost is a just a relative value, and it is not meant to be literal. Calls with higher costs are more expensive to make than calls with lower costs.

The cost of an outgoing call is determined by the following conditions:

The number being dialed.

The outgoing translation rules for the switch through which the call is being made. The outgoing translation rules are configured using the Voice Mail System Configuration (VMSC) application. For detailed instructions for configuring the translation rules see PBX Configuration - SIP Tab (IP SIP) - Translation Rules Dialog Box.

When a canonical phone number is converted into a switch-native number using the phone number translation rules, a corresponding cost is also determined. If the call cost is less than or equal to the limit that you set in this field, then system dials the number, else the system rejects the call.

The costs specified for outbound calls control whether, for example, a subscriber is allowed to call just the local extensions, or national, international, or premium rate numbers.

Enter appropriate values to configure the costs for outbound calls in the following fields:

Maximum costs for Automated Attendant outcalls These costs determine the numbers that can be dialed by external callers using the Automated Attendant. Enter a number between 0 and 10000. The default is 100.

Maximum costs for subscriber outcalls These costs determine the external numbers that can be dialed by the subscribers. Enter a number between 0 and 10000. The default is 100.

The maximum costs are associated with restriction on whether, for example, a subscriber can make internal, national, or international calls.

For example, if 100 is the cost associated with internal calls, then the subscriber is only allowed to call local extensions.