- Alarm Origination Use this setting to control whether Modular Messaging attempts to reach back to Avaya Technical Support for automated maintenance. Select the appropriate option button:
- Inactive Select so that no alarm notifications are sent to Avaya.
These fields in the tab are then grayed out: Suppress alarm notifications, Clear Alarm Notification, and Send alarm at this level or higher.
|
Note:
If you select this option, you can still view alarm logs on the MAS.
|
|
- SNMP Select to send alarm traps to an NMS using SNMP. This is IP-based alarming.
- Modem dialout Select to use the INADS tool to send alarm notifications to an alarm collection server for analysis and corrective action. This is modem-based alarming
.
- Internet (Default for new installations) Select to relay alarm information back to Avaya through the Internet capabilities of the Avaya SPIRIT Agent.
- Suppress alarm notifications (Default Off) Select to temporarily suppress all alarm notifications for the voice mail domain.
If selected, this setting overrides the setting for individual MASs in the MAS - Serviceability dialog box, General tab. If not, the per-MAS settings apply. For more information see VMSC - MAS - Serviceability - General Tab.
|
Note:
You would typically select this setting, if you were engaged in VMD-wide maintenance and/or repair activities that would result in the generation of additional alarms and errors. In this situation, be sure to remember to clear this check box when you are finished, otherwise alarm notifications will not resume.
|
|
- Clear Alarm Notification (Default On) Select to be notified when all alarms on the system are corrected and cleared.
- Send alarm at this level or higher: Select the level at which alarm notifications are sent out:
- Minor (Default) Select to send major and minor alarms.
- Major Select to send only major alarms.
- All Select to send major alarms, minor alarms, and warnings to Operations, Administration, and Maintenance (OAM) destinations, and to send major and minor alarms to INADS destinations.
|
Note:
Warnings are for customer information only; they are not sent to Avaya Technical Support.
|
|
- When stopping the MAS service This section determines how the system will behave, when the MM Messaging Application Server service is being stopped.
For more information on Modular Messaging services, see MAS - Modular Messaging (MM) Services.
- Wait for ports to become idle Select to allow ports that are in use to become idle before being taken offline. As ports become idle, then they are taken offline. This allows for a more graceful shutdown of the system and should be used whenever possible.
|
Note:
When this option is selected, if the system tries to stop the MM Messaging Application Server service, it waits until all ports are idle. As a result, some length of time may pass before service is actually stopped. During this period, while ports are becoming idle, your Windows operating system may display a timeout error 1053. Ignore this error. The stopping process is unaffected by this message and the service will stop according to the parameters you have set.
|
|
This option activates the Wait indefinitely and Wait for (minutes) options.
- Wait indefinitely Select so that the system will wait until all ports are idle before shutting down the MM Messaging Application Server service. If possible, this is the most desirable option, as it allows all ports to be taken offline naturally, with no interruption of service for the user.
- Wait for (minutes) (Default) Select to set the number of minutes that the system will wait before breaking port connections and shutting down, whether ports are in use or not. In this case, ports that become idle within the time limit are taken offline, but ports that are still busy at the end of the time limit are forcibly taken offline.
Enter the number of minutes in the field to the right. The default is 10.
- Stop immediately (Default) Selecting this option causes all ports that are in use, when the MM Messaging Application Server service is being stopped, to immediately be taken offline. This should only be used as a last resort, as it interrupts any calls that may be in progress.
