Contents |
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.
The Alarms Tab displays the list of all the available alarm profiles, alarms generated in the network with information about the reason for the alarm (for instance, ASR less than a particular value), the timestamp of the alarm and its severity.
Alarms tab displays two views - Summary View and Detailed View. Summary View displays the list of all Alarm Profiles. Detailed View provides the list of all the individual alarms.
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:
Incomplete Calls - when calls go incomplete consecutively and when the number of such consecutive incomplete calls go beyond a certain value
Average Length of Call (ALOC) - when the ratio between the sum of the time duration of all successful calls and the number of all successful calls goes below or beyond the desired value
Answer Seizure Ratio (ASR) - when the ratio between successfully connected calls to attempted calls goes beyond the desired value
Average Answer Delay- when the difference in time duration between successful initiation of call and the time taken by the person on the other end to actually attend the call (i.e. delay in answering the call), goes beyond a particular value
Concurrent calls- An alarm can be generated if the number of concurrent calls goes beyond a certain value for a certain number of times
Voice Bandwidth Utilization - when the call traffic in the network goes beyond a particular limit making heavy voice bandwidth utilization
Call Set up Time - The time from the initiation of a call request to the beginning of the call ringing tone received. An alarm is raised when the call set up time is more than the desired delay (in seconds). This alarm profile is available only for Sniffer interface.
SIP Error Codes - An alarm is triggered when the number of calls with same or similar SIP error codes is greater than the specified number of calls
Jitter - An alarm can be generated when jitter values increases beyond a specified milliseconds
Packet Loss - An alarm is raised when the packet loss is greater than the specified percentage
Call Volume - An alarm can be triggered when the call count is below or more than the desired limits in the given time interval
Disconnect Time - An alarm can be generated when the number of calls with same disconnect time is greater than the specified number of calls
Talk Time - An alarm can be generated when the Total Talk time is less than or greater than the talk time value defined by the administrator
R Factor - When the R Factor less than or between the specified values by the administrator, an alarm can be triggered off to inform the administrator
MOS - An alarm can be triggered when the MOS value is less than or within the range specified by the administrator
MOS Trend - The trend of MOS over a period of time can be taken as the basis for generating an alarm. For example, if the MOS trend during a period of say, three days falls below a certain range specified by the administrator, an alarm can be generated
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.
Go to "Alarms" tab
Click the link "Add Alarm Profile"
In the 'Add Alarm Profile' UI that opens, provide a "Name" for the new profile in the text field
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
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,
set the 'Sampling Interval' - that is the time interval at which the VQManager database has to be queried for details. You can specify the time interval in minutes, hours or days.
set the 'Time Filter' - that is the data that got accrued during which time span has to be considered - whole day or business hours or non-business hours or your own custom time period
if you do not wish to consider the data accrued during weekend (Saturday & Sunday), select the check box "Exclude Weekends"
click "Set"
Define the "Threshold" value for the chosen condition. When data touches or goes beyond the threshold value specified, alarm will be generated
For Incomplete Calls
In the textfield, specify the number of consecutive incomplete calls beyond which you would like to receive an alarm. Choose the severity which you would like to assign (Critical/Major/Warning). In addition, specify a meaningful message for the alarm. For example: "Incomplete Calls exceeded 10". This message would be highly helpful in understanding the type of problem when you receive the alarm
You also have the option to generate repeat alarms when the number of consecutive calls reach the multiples of the threshold value. For example, if you have set 10 as the threshold value for incomplete calls, the alarm will be generated when 10 consecutive calls go incomplete. If the problem continues and number of incomplete calls grow further and it crosses 20 (the multiple of 10 which was set as the threshold value), another alarm would be generated. This would continue for 30, 40 and so on. If you want to have this option, just check the checkbox "Repeat Alarm for same intervals". This option is available only for 'Critical' category alarms. By default, this option is enabled.
When a successful call comes after a number of consecutive incomplete calls, a Clear Alarm will be generated with the message "A successful call received after XX consecutive incomplete calls". However, it is to be noted that a Clear Alarm for incomplete calls will be generated for a profile, only if the profile had generated at least one alarm.
You can make use of any or both the remaining two severities (Major/Warning) and define different threshold values for them. In such a case, click the link "Add Threshold" and repeat the above steps
Email Notification: You have the option of automatically sending an email to notify the desired recipients when an alarm is generated. To use this option, you need to enable the option "Send Email to" and specify the email id in the textfield. Once you enable this option, email notification would be sent to the specified recipients upon the generation of the particular alarm. The email message will contain details such as Subject, Alarm ProfileName, severity, alarm message, time of creation of the alarm and other details
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
Note: The incomplete error calls does not include "Request Terminated" calls (SIP error code: 487). |
For ALOC
In the text field, specify the ALOC value
in seconds (sum of the duration of all successful calls divided by the
number of all successful calls) below or beyond which you want to generate
the alarm. In the drop-down menu, choose '<' for ALOC below the specified
value and '>' for ALOC going beyond the specified value. In the adjacent
text field define the number of calls beyond which the alarms is to be
generated. Choose the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"ALOC falling below 30 seconds for more than 5 calls". This
message would be highly helpful in understanding the type of problem when
you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different threshold values for
them. In such a case, click the link "Add Threshold" and repeat
the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For ASR
In the text field, specify the ASR value in
percentage (the ratio between successfully connected calls to attempted
calls) below which you want to generate the alarm. In the adjacent text
field define the number of calls beyond which the alarms is to be generated.
Choose the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"ASR falling below 30%". This message would be highly helpful
in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different threshold values for
them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other detail.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Average Answer Delay
In the text field, specify the maximum permissible
Average Answer Delay value in seconds (the difference in time duration
between successful initiation of call handling by the device and the time
taken by the person on the other end to actually attend the call (i.e.
delay in answering the call)) beyond which you want to generate the alarm.
Also enter the number of calls beyond which the alarms is to be generated.
Choose the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"Average Answer Delay going beyond 40 seconds". This message
would be highly helpful in understanding the type of problem when you
receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different threshold values for
them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Concurrent Calls
In the first text field, enter the value of
'number of concurrent calls' beyond which the alarm is to be generated.
Also enter the value for the number of occurrences in the next input field.
For example : "Number of concurrent calls greater than 50 and
occurrences more than 5". This condition will generate an alarm if
the number of concurrent calls goes beyond 50, 5 times. Choose the severity
you would like to assign and also enter an appropriate message. This message
would be highly helpful in understanding the type of problem when you
receive the alarm. The default sampling interval duration for concurrent
calls based alarms will be 5 minutes.
You can make use of any or both the of remaining
two severities (Major/Warning) and define different threshold values for
them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Call Set-up Time
This is the only alarm profile that is unavailable for CDR Interface.
In the text field, specify the call setup
time in seconds and also set the number of calls beyond which you would
like to receive an alarm. Choose the severity which you would like to
assign (Critical/Major/Warning). In addition, specify a meaningful message
for the alarm. For example: "Call Set up Time is more than 10 seconds
for more than 5 calls". This message would be highly helpful in understanding
the type of problem when you receive the alarm
You can make use of any or both the remaining
two severities (Major/Warning) and define different threshold values for
them. In such a case, click the link "Add Threshold"
and repeat the above steps
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to check the option "Send
Email to" and specify the email id in the text field. Once you enable
this option, email notification would be sent to the specified recipients
upon the generation of the particular alarm. The email message will contain
details such as Subject, Alarm Profile Name, severity, alarm message,
time of creation of the alarm and other details
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps
For Voice Bandwidth Utilization
In the text field, specify the Voice
Bandwidth Utilization value and select the units from drop down menu (Kbps/Mbps/Gbps)
beyond which you want to generate the alarm. Choose the severity which
you would like to assign (Critical/Major/Warning). In addition, specify
a meaningful message for the alarm For example: "Voice Bandwidth
Utilization going beyond 100 mbps". This message would be highly
helpful in understanding the type of problem when you receive the alarm.
You can make use of any or both
the remaining two severities (Major/Warning) and define
different threshold values for them. In such a case, click the link "Add
Threshold" and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For SIP Error Code
In the text field, specify the SIP error code
for which you would like to raise the alarm. For raising the alarm for
the exact SIP error code chose 'equals' in the drop down menu or use 'like'
to get alarms for SIP error code from similar series. There is also
provision to 'exclude' SIP code in 'like' condition. Specify the
number of calls beyond which you would like to receive an alarm. This
will raise the alarm when the number of calls with similar / same SIP
error code are beyond the tolerable number of calls specified by the administrator.
Choose the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"More than 50 calls have Sip Error Code: 400". This message
would be highly helpful in understanding the type of problem when you
receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Jitter
In the text field, specify the jitter threshold
(in milli seconds) beyond which you would like to receive an alarm. Choose
the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"The Jitter is greater than 10ms". This message would be highly
helpful in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Packet Loss
In the text field, specify the packet loss
criterion (in percentage) beyond which you would like to receive an alarm.
Choose the severity which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"Packet loss greater than 5%". This message would be highly
helpful in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For MOS
The MOS alarm can be generated when the MOS
value is less than or between the ranges defined by the administrator.
To set the alarm, define the criteria by entering the MOS value below
which you want the alarm to be activated. Alternatively, you can also
define the MOS range between which the alarms are to be raised. Choose
the severity, which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"The MOS less than 2.9". This message would be highly helpful
in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define
different threshold values for them. In such a case, click the link "Add
Threshold" and repeat the above steps.
Email Notification: You have the option of automatically sending an email to notify the desired recipients when an alarm is generated. To use this option, you need to enable the option "Send Email to" and specify the email id in the textfield. Once you enable this option, email notification would be sent to the specified recipients upon the generation of the particular alarm. The email message will contain details such as Subject, Alarm ProfileName, severity, alarm message, time of creation of the alarm and other details
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For MOS Trend
The MOS alarm can also be generated based
on the MOS trend. For example, if the MOS value goes below or stays in
between the range defined by the administrator beyond a specified number
of times, an alarm can be generated. To set the alarm, define the criteria
by entering the MOS value below which you want the alarm to be activated.
Alternatively, you can also define the MOS range between which the alarms
are to be raised. Also, specify the number of times the MOS trend could
continue, beyond which you would wish to generate an alarm. Choose the
severity, which you would like to assign (Critical/Major/Warning). In
addition, specify a meaningful message for the alarm. For example: "The
MOS less than 2.9 for more than 3 times". This message would be highly
helpful in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define
different threshold values for them. In such a case, click the link "Add
Threshold" and repeat the above steps.
Email Notification: You have the option of automatically sending an email to notify the desired recipients when an alarm is generated. To use this option, you need to enable the option "Send Email to" and specify the email id in the textfield. Once you enable this option, email notification would be sent to the specified recipients upon the generation of the particular alarm. The email message will contain details such as Subject, Alarm ProfileName, severity, alarm message, time of creation of the alarm and other details
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For R Factor
The R Factor alarm can be generated when the
R Factor value is less than or between the ranges defined by the administrator.
To set the alarm, define the criteria by entering the R Factor value below
which you want the alarm to be activated. Alternatively, you can also
define the R Factor range between which the alarms are to be raised. Choose
the severity, which you would like to assign (Critical/Major/Warning).
In addition, specify a meaningful message for the alarm. For example:
"The R Factor less than 90". This message would be highly helpful
in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define
different threshold values for them. In such a case, click the link "Add
Threshold" and repeat the above steps.
Email Notification: You have the option of automatically sending an email to notify the desired recipients when an alarm is generated. To use this option, you need to enable the option "Send Email to" and specify the email id in the textfield. Once you enable this option, email notification would be sent to the specified recipients upon the generation of the particular alarm. The email message will contain details such as Subject, Alarm ProfileName, severity, alarm message, time of creation of the alarm and other details
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Call Volume
The call volume alarm can be generated for
both increase in call volume as well as decrease in the call volume. To
set the alarm, define the criteria by entering the number of calls beyond/
below which you want the alarm to be activated. Choose the severity which
you would like to assign (Critical/Major/Warning). In addition, specify
a meaningful message for the alarm. For example: "The Call volume
less than 50 calls". This message would be highly helpful in understanding
the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Disconnect Time
In the text field, specify the number of calls
disconnected, at a specific moment of time, beyond which you would like
to receive an alarm. Choose the severity which you would like to assign
(Critical/Major/Warning). In addition, specify a meaningful message for
the alarm. For example: "Disconnect Time greater than 15". This
message would be highly helpful in understanding the type of problem when
you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
For Talk Time
The Talk Time alarm can be generated for both
increase in Total Talk Time as well as decrease in the Talk Time. To set
the alarm, define the criteria by entering the number of call minutes
beyond/ below which you want the alarm to be activated. Choose the severity
which you would like to assign (Critical/Major/Warning). In addition,
specify a meaningful message for the alarm. For example: "The Total
Talk Time is less than 50 minutes". This message would be highly
helpful in understanding the type of problem when you receive the alarm.
You can make use of any or both the remaining
two severities (Major/Warning) and define different
threshold values for them. In such a case, click the link "Add Threshold"
and repeat the above steps.
Email Notification: You have the option of
automatically sending an email to notify the desired recipients when an
alarm is generated. To use this option, you need to enable the option
"Send Email to" and specify the email id in the text field.
Once you enable this option, email notification would be sent to the specified
recipients upon the generation of the particular alarm. The email message
will contain details such as Subject, Alarm Profile Name, severity, alarm
message, time of creation of the alarm and other details.
SNMP Trap Forwarding: The administrator can enable the VQManager to generated SNMP traps on specific alarms. This will help in integrating the VQManager alarms with any higher-level NMS like ManageEngine OPManager. The VQManager allows the administrator to set up the list of SNMP trap listeners to forward the SNMP traps. By specifying the required SNMP parameters (viz., hostname, port, community, version etc.,), the embedded VQManager SNMP agent can generate appropriate SNMP traps and forward to the defined entries. Currently the VQManager SNMP agent can generate a SNMP V1 and SNMP V2C traps.
Click 'Add'
The required Alarm profile has been created
Note:
|
You can edit an existing alarm profile, at any point of time.
To edit an alarm profile,
Go to "Alarms" tab
In the Summary View, all the alarm Profiles available at the moment get listed
Click the edit icon against the name of the profile that is to be edited
Alarm Profile Name and based on information are non-editable
Carry out the required changes
Click "Update"
You can delete the alarm profiles that are no longer needed, at any point of time.
To delete an alarm profile
Go to "Alarms" tab
In the Summary View, all the alarm Profiles available at the moment get listed
Click the icon against the name of the profile that is to be deleted
The Alarm profile would be deleted once and for all
Note: When you delete an alarm profile, all the alarms that were associated with the particular profile would get deleted. |
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 |
This is a summary of the different alarms that have been generated during the time period as set in the calendar and is found on the left hand side below the "Quick Links".
All categories of alarms: 'Clear', 'Warning', 'Major' and 'Critical' are shown including the 'Total Alarms' generated in the selected time period.
You can view more details of respective alarms by clicking on the linked number next to the alarm profile name (under corresponding alarm categories).
Next Section covers ....
|
Copyright © 2011, ZOHO Corp. All Rights Reserved.