Alarms Tab - Alerting the Administrator

Contents

Overview

When something goes wrong with the call quality, it is important that the administrator is alerted on the same in order to initiate some corrective action. VQManager can generate alarms when a particular vital parameter goes beyond a particular value - for instance, number of incomplete calls going beyond a particular value. You can specify the criteria based on which the alarms are to be generated. This can be done by creating Alarm Profiles.  

Creating Alarm Profiles

As stated above, Alarm Profiles are created to define the condition based on which alarms are to be generated. Alarms can be generated when the VoIP network suffers problems in any or all of the following  aspects:  

While specifying the conditions for generating Alarms, you can also set the severity for the alarm, For every alarm generation condition, you can have any of the three levels of severity - Critical, Major and Warning. Even within one category (say incomplete calls), you can configure three different alarms, one for each severity and you can define different threshold limit for each severity. 

 To create an Alarm Profile, 

  1. Go to "Alarms" tab

  2. Click the link "Add Alarm Profile"

  3. In the 'Add Alarm Profile' UI that opens, provide a "Name" for the new profile in the text field

  4. Choose the base condition for generating the Alarm from the drop-down menu. There are several options such as Incomplete Calls, ALOC, ASR, Average Answer Delay, Voice Bandwidth Utilization etc. Choose the desired option

  5. Define "Time Filter" criteria - that is the data getting accrued during a particular time period that has to be considered for generating the alarm. For example, one would like to generate the alarms for the abnormal conditions happening only during business hours. Or some would not like to generate alarms for the happenings during the weekends. For all such cases, you can define 'Time Filter' criteria. To define this, click the link "Time Filter" present on the right hand side corner of the 'Add Alarm Profile' UI. In the UI that opens,

  6. Define the "Threshold" value for the chosen condition. When data touches or goes beyond the threshold value specified, alarm will be generated

Defining Threshold Values

For Incomplete Calls

Note:

The incomplete error calls does not include "Request Terminated" calls (SIP error code: 487).


For ALOC

 

  For ASR

 
 

   For Average Answer Delay

 

 

    For Concurrent Calls

 

 

  For Call Set-up Time

 
 

  For Voice Bandwidth Utilization

 

 

For SIP Error Code

 

 

  For Jitter

 

 

For Packet Loss

 

 

For MOS

 

 

For MOS Trend

 

 

For R Factor

 

 

For Call Volume

 

 

 For Disconnect Time

 

 

For Talk Time

 
 
 

Note:

  • Call Set Up Time is available only for Sniffer Interface.

  • Each Alarm Profile Name should be unique.

  • The alarm message field is mandatory.

  • At least one threshold definition should be added and a maximum of three can be added with different severities.

  • More than one threshold cannot be added with same severity for a particular profile.

  • For ALOC, ASR, Average Answer Delay, SIP Error Codes, Disconnect Time, Call Volume, Packet Loss, Jitter and Voice Bandwidth Utilization Time the default time interval for raising the alarm is 60 minute while for Talk Time the default time interval is 1 day.

  • For generating alarms for ALOC, ASR, Average Answer Delay, SIP Error Codes, Disconnect Time, Call Volume, Packet Loss, Jitter and Voice Bandwidth Utilization Time a scheduler fetches data. The data is fetched at half of the time interval, set for sample duration, by the administrator i.e. If the administrator wants the alarm alert every 60 minutes, then the scheduler will fetch data every 30 minutes.

  • The order of triggering of alarms is done in the following way: For a single profile, you can define three different thresholds with different severities - CRITICAL, MAJOR & WARNING. Whichever severity has been defined first in the UI, it will get executed first. If WARNING is defined first in the UI, it will get executed first and other severities are executed in the same order as created in the UI. So, it is advisable to define 'CRITICAL' as the first severity. (For example, assume that you have created an ASR profile to raise a WARNING alarm when ASR goes below 60 per cent (first severity in the UI). Assume further that you have defined the second severity to generate a CRITICAL alarm when ASR falls below 50 per cent. Also assume that ASR suddenly touches 40 percent. Only a WARNING alarm would be generated first even though the condition falls under CRITICAL category).

Editing Alarm Profiles

You can edit an existing alarm profile, at any point of time.

 To edit an alarm profile,

Deleting Alarm Profiles

You can delete the alarm profiles that are no longer needed, at any point of time.

 To delete an alarm profile

 

Note: When you delete an alarm profile, all the alarms that were associated with the particular profile would get deleted.

Pre-created Alarm Profiles

By default, VQManager provides three pre-created alarm profiles namely ALOCProfile, ASRProfile, AverageAnswerDelayProfile. 

 

Profile Name

Description

ALOCProfile

ALOC profile has been created for raising a critical alarm when ALOC exceeds 1200 seconds. Similarly, when ALOC falls below 25 seconds, a Major alarm and when it exceeds 900 seconds, a Warning alarm would be generated. You can edit this default profile and set your own condition

 

ASR Profile

ASR profile has been created for raising a critical alarm when ASR goes below 40 per cent. Similarly, when ASR falls below 50 per cent, a Major alarm and when it is less than 60 per cent, a Warning alarm would be generated. You can edit this default profile and set your own condition

AverageAnswerDelayProfile

 
 
 

This profile has been created for raising a critical alarm when it goes beyond 60 seconds. Similarly, when Average Answer Delay exceeds 45 seconds a Major alarm and when it goes above 20 seconds, a Warning alarm would be generated. You can edit this default profile and set your own condition

 
 
 

Total Alarms

   
 

Next Section covers ....

 

 


Copyright © 2011, ZOHO Corp. All Rights Reserved.